On Mon, 12 Oct 2026 22:12:26 GMT, Marius Hanl <[email protected]> wrote:
>> 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.
css: test:on { prop: 5 }
1. set style test:on, applyCss
2. check value 5
3. set prop settable=false
4. set pseudoclass :on to false via pseudoClassStateChanged()
5. applyCss
6. check value 5
7. set settable=true
8. set :on to true
9. applyCss
10. set :on to false
11. check value, should be default
-------------
PR Review Comment: https://git.openjdk.org/jfx/pull/2343#discussion_r4252829143
