Lots of things might be good ideas. I'm rather skeptical of the cost /
benefit of implementing a new CSS parser. This would be a large effort
and run a significant risk of regression, especially since CSS is a
fragile area (although parsing less so than the runtime CSS processing).
-- Kevin
On 8/26/2024 10:24 AM, Andy Goryachev wrote:
Michael:
This might be a good idea. A few questions:
* can we create stylesheets programmatically without parsing (i.e.
construct the token tree directly)?
* would it be possible to add a diagnostic (at the moment of
applyCSS()) to show the actual rule(s) being used?
* are we going to track the evolution of
https://www.w3.org/TR/css-syntax-3/ "spec"?
* are we going to clarify the w3 "spec" (what is the value of "EOF
code point"?)?
* are there incompatibilities between web-style CSS and FX-style CSS?
* what is the testing strategy?
Thank you
-andy
*From: *openjfx-dev <openjfx-dev-r...@openjdk.org> on behalf of
Michael Strauß <michaelstr...@gmail.com>
*Date: *Sunday, August 25, 2024 at 20:45
*To: *openjfx-dev <openjfx-dev@openjdk.org>
*Subject: *New CSS parser for JavaFX
I've written up a proposal to implement a new CSS parser for JavaFX:
https://gist.github.com/mstr2/f416996caf48e11193f0b6a5883a3926
The goal is not add new features at this point, but to resolve some
long-standing issues with the existing CSS parsing (though if you read
carefully, you might spot a new feature).
I'm interested in your opinion whether this is a good idea to move
forward.
