In general the closure stylesheets library uses JavaCC to generate a parser from a grammar. So it is not super terrible to update it if someone has JavaCC experience. But personally I think CSS is moving pretty fast and a more flexible solution would be better, so you can play with new CSS features without waiting for someone to update a grammar. Even though I created a local project to explore some ideas nobody is actively working on improving the situation with CssResource.
With regard to bounties: So far there hasn't been any as far as I know. But of course you can hire someone to fork and update closure stylesheets and then let us know about the fork. If you plan to do that it might be a good idea to make sure its not an AI agent who effectively wrote the code (unclear license issues). In the issue https://github.com/gwtproject/gwt/issues/10036 is a link to a closure stylesheets fork which did some continued development so maybe the maintainer would be a good candidate to ask. There is also the company Vertispan which can be paid for GWT related services.
-- J.
cbruno...@gmail.com schrieb am Mittwoch, 25. Februar 2026 um 01:12:25 UTC+1:
Im using UiBinder and source in a CssResource using <ui:style> in the .ui.xml file. I am always hitting a walling using modern CSS like :not selectors or var. I know some workarounds to get these to work but im wondering what would it take to really make CssResource great again. Does the community here accept bounties?
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/19e91f3e-b74e-4d54-a103-e4ac3e9bfde9n%40googlegroups.com.
No comments:
Post a Comment