News for hackers. Stuff that matters.
Re:Full-Bleed Layout Using CSS Grid by artificial on Monday October 05, 2020 @09:34PM (#24693968)
Wouldn’t that be Chrome? The ubiquity leads to lazy developers testing only on it. Maybe some fancy SVGs saying “Best viewed on Chrome!” To really rub it in :)
Re:Full-Bleed Layout Using CSS Grid by DarkWiiPlayer on Tuesday October 06, 2020 @02:53AM (#24695310)
> SVGs saying “Best viewed on Chrome!”

HA! Chrome absolutely SUCKS at displaying SVGs. I rarely use them and I've already found two stupid bugs.

One super weird one (probably too much caching) where an animated element in a <use> clone didn't inherit colours while its non-animated siblings do. This one is fixed now.

What isn't fixed yet is that `filter: hue-rotate(90deg)` applied to an SVG child element doesn't do anything (in firefox it does), is a pain in the ass because SVG filters, while more powerful, are much harder to set up.

Re:Full-Bleed Layout Using CSS Grid by progers7 on Tuesday October 06, 2020 @08:26AM (#24696960)
SVG filter support in Chromium is actively being worked on, primarily led by an incredible engineer at Opera ([email protected]). This work has been ongoing for almost a year and should complete in Q4. Please star https://crbug.com/109224 for updates (stars also help prioritization).
Re:Full-Bleed Layout Using CSS Grid by realusername on Tuesday October 06, 2020 @03:50AM (#24695568)
Safari also has its share of SVG bugs, like this one: https://stackoverflow.com/questions/31150919/svg-background-...
Re:Full-Bleed Layout Using CSS Grid by artificial on Tuesday October 06, 2020 @11:23AM (#24698654)
Going to codepen this later and see what’s up. I haven’t used them beyond toy setups since it’s usually a hassle, I always get inspired by the Stripe site.
Re:Full-Bleed Layout Using CSS Grid by greggman3 on Monday October 05, 2020 @10:18PM (#24694181)
No, the definition of "the new IE" is to not support the latest features.

Pick some other phrase for "most popular"

Re:Full-Bleed Layout Using CSS Grid by lucideer on Tuesday October 06, 2020 @06:09AM (#24696236)
The definition of "the new IE" is not not supporting the latest features (IE had plenty of "new" features—see e.g. filters, VML, XMLHttpRequest). The issue with IE was that it supported it's own proprietary features without consultation nor coordination with competitors. Something it was only able to do due to its market monopoly.

Yes, Chrome does this too.

It's slightly better in that it tends to submit them to standards bodies after implementing them, but most of the time that's WHATWG which is a much less democratic body than others, and mostly Google-led. Either way Chrome's market monopoly leave competitors with little choice in the standards process.

Re:Full-Bleed Layout Using CSS Grid by tannhaeuser on Tuesday October 06, 2020 @03:01AM (#24695332)
Yeah "web standards" my ass - with WHATWG 100% just being Chrome devs, and W3C a pay-as-you-go wannabe "standardization body" financed by Google (and long out of the game of doing anything meaningful except CSS) so-called web standards are more of a monopolization and extortion instrument than anything else. Web heads seriously need to wake up rather than making it ever more complicated.
Re:Full-Bleed Layout Using CSS Grid by keeganpoppen on Tuesday October 06, 2020 @01:13AM (#24694905)
he is 100% right that IE's ubiquity is what caused the problem to begin with. well, that and microsoft getting arrogant because of it.