On Mon, 12 Oct 2026 22:06:32 GMT, Andy Goryachev <[email protected]> wrote:
>>> btw, will this scenario work if the css changes pseudostyle? >> >> probably not, thats why setting a value sometimes looks like you overwrite >> the style, while in reality the next real css apply will change it back >> again (and thats why binding is actually a valid way to force a style to not >> get overwritten by CSS). > > well, it does not. I cannot show you the test but basically do this: > > 1. use a pseudoclass to change the property > 2. make the property not settable > 3. remove the pseudoclass > 4. make the property settable > 5. reapply, and remove the same style > > (edit: it's a regression, the test passes in master and fails with this PR) What does 'remove the same style' mean? Also, is this related to this PR / even a bug? Setting or binding a property, as outlined above is not applying CSS automatically, so you can do all kind of weird inbetween states by that. It is how it is, I'm also on the side that developers calling the setter should win, but probably not possible anymore, probably for the mailing list for which I don't have time currently. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/2343#discussion_r4252777865
