top | item 24692579

(no title)

ss3000 | 5 years ago

Widespread flex gap support will probably eliminate 95% of grid usage in my apps today: https://caniuse.com/flexbox-gap

And what a surprise, it's just Safari holding us back again. =_=

discuss

In fairness, this feature was only released in Chrome a couple of months ago, and has in the past week been merged into WebKit: https://trac.webkit.org/changeset/267829/webkit

ss3000|5 years ago

Fair enough, I guess both Chrome and Safari were holding us back until a few months ago haha.

Really ecstatic to see that it's going to be in Safari soon though! Thank you so much for sharing! Really made my day.

This is why I love Hacker News.

desert_boi|5 years ago

Chrome got in in May finally...Firefox has had it for years. One thing I really missed in Chrome and Safari.

gkilmain|5 years ago

Awesome - didn't know this was a thing.

Dahoon|5 years ago

The new IE.

artificial|5 years ago

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 :)

earthboundkid|5 years ago

You mean the common JS environment that doesn’t support fetch, Node?

russelg|5 years ago

Very disingenuous of you. IE was a trashfire because it refused to do anything in a standard way, meaning it had to be specially catered for. Safari is slow to follow the standards but at least its compliant. A engine that isn't Chrome is very essential for keeping the web open, especially since Firefox user share keeps going down.

ehnto|5 years ago

Firefox and Chrome still don't agree on how tables should work.