On Tue, 30 Jun 2026 19:24:04 GMT, Andy Goryachev <[email protected]> wrote:
> I don't know whether a CSR is needed, since the actual format has not been > documented, but the fact that multiple tests fail with this change indicate > that the applications that rely on the exact string (and not on > `.contains()`) will break. But note that the tests did check for whole `String`. If we would change e.g. `Node.toString()`, then tests will also fail. If we would change a `toString()` method from any other list (e.g. `getChildren`), then there might be a test that checked the excact pattern - but not because it is needed but because we have tests to even check the whole `String`. A normal `contains` on the list will work as before, even a `contains` on the `String` will work as before. Just that the whole sequence looks like one would expect from a list. I can't see a reason why application would use the value from `toString` other than debugging ------------- PR Comment: https://git.openjdk.org/jfx/pull/2191#issuecomment-4853956267
