3 ms·
Far from being ready when only one major browser supports it. If you want this, you should vote for it to be focused on for interop-2026 https://github.com/web
by culi 11mo ago
Far from being ready when only one major browser supports it. If you want this, you should vote for it to be focused on for interop-2026
https://github.com/web-platform-tests/interop/issues https://github.com/web-platform-tests/interop/issues
Right now, the leading CSS proposals are `@container style()`, `corner-shape` and `break-after`
https://foolip.github.io/interop-reactions/ https://foolip.github.io/interop-reactions/
- hdjrudni 11mo agoYeesh.. I've definitely tried using break-after and being disappointed it didn't work properly. The amount of hoops I had to jump through to get things to print properly on paper...
- fuzzfactor 11mo ago>The amount of hoops I had to jump through to get things to print properly on paper... Anybody know how that compares to Report Definition Language? https://learn.microsoft.com/en-us/sql/reporting-services/reports/report-definition-language-ssrs https://learn.microsoft.com/en-us/sql/reporting-services/rep... Seems like an awfully scattered shitshow just to arrive at a typical "What You See Is Not What You Get" result. And this one is made for printouts.
- culi 11mo agoAgreed. This has come up multiple times during my job. It's gotten to the point where we had a microservice running that spun up selenium and printed the dom and then sent that pdf back to the front-end all just to make consistent print outputs. I've read tech blogs of others doing just that too so it's not uncommon. Unfortunately the test set of wpt does not have the capability to cover printed matter so relief isn't coming any time soon
- StoneAndSky 11mo agoThe People have spoken, and they want squircles.