CSS Grid Lanes • Hacker News Board

Re: CSS Grid Lanes

#101

Post by culi » Sat, Dec 20, 2025, 3:10 AM UTC

meowface wrote: post #73

culi wrote: post #27

Props to the Safari team. They surprised us all when they suddenly shot to the top of interop-2025 this October https://wpt.fyi/interop-2025

I hope they add WebTransport support soon.

voting for interop 2026 is active now. I see somebody has already submitted a proposal for it

https://github.com/web-platform-tests/interop/issues/1121

Re: CSS Grid Lanes

#102

Post by hoten » Sat, Dec 20, 2025, 3:11 AM UTC

culi wrote: post #27

Props to the Safari team. They surprised us all when they suddenly shot to the top of interop-2025 this October https://wpt.fyi/interop-2025

I wonder if Ladybird has explored running these interop tests yet. Or maybe these are just a subset of WPT?

Re: CSS Grid Lanes

#103

Post by wackget » Sat, Dec 20, 2025, 3:12 AM UTC

I wish they'd release CSS Gap Decorations: https://developer.chrome.com/blog/gap-decorations

I'm tired of having to use stupid hacks to get nice-looking borders between flex/grid items.

Re: CSS Grid Lanes

#104

Post by open592 » Sat, Dec 20, 2025, 3:31 AM UTC

hoten wrote: post #102

culi wrote: post #27

Props to the Safari team. They surprised us all when they suddenly shot to the top of interop-2025 this October https://wpt.fyi/interop-2025

I wonder if Ladybird has explored running these interop tests yet. Or maybe these are just a subset of WPT?

You can edit the "products" represented in the table and add "Ladybird" to the list. [1]

Their result is: 1974740 / 2152733 (91%)

They also have their own dashboards tracking this [2]

[1] https://wpt.fyi/results/?product=ladybird

[2] https://grafana.app.ladybird.org/public-dashboards/2365098a1...

Re: CSS Grid Lanes

#105

Post by halapro » Sat, Dec 20, 2025, 3:37 AM UTC

al_borland wrote: post #53

culi wrote: post #27

Props to the Safari team. They surprised us all when they suddenly shot to the top of interop-2025 this October https://wpt.fyi/interop-2025

This seems like a bit of a trend with Safari. Around big releases Apple will announce how Safari is the best at X, but other times of the year it gets a lot of flack. I assume this is due to Safari’s more traditional release schedule vs other browsers continuously shipping feature updates.

Safari has been releasing a lot more often than it used to. My personal gripe with Safari is how they decided to deal with extensions, forcing every developer through their hellish App Store submission experience.

Re: CSS Grid Lanes

#106

Post by halapro » Sat, Dec 20, 2025, 3:40 AM UTC

emilbratt wrote: post #56

I always thought that the masonry layout looked good but made it harder to get a good overview of the images.

A lot of web "design" is about how it looks rather than how usable it is. At no point any stakeholder stops and actually uses the product, they scroll up and down, enjoy the pointless "scroll in" animations and say "kewl". Never mind the text that is at 50% opacity until you scroll to the exact intended point, because nobody actually attempted to read it.

Re: CSS Grid Lanes

#107

Post by rendaw » Sat, Dec 20, 2025, 4:00 AM UTC

ChadNauseam wrote: post #46

culi wrote: post #27

Props to the Safari team. They surprised us all when they suddenly shot to the top of interop-2025 this October https://wpt.fyi/interop-2025

I didn't realize it was tracked like this, but I have noticed that as of iOS 26, Safari has gotten a huge number of great web features. It has WebGPU of course, but many small things like fixing up missing parts of the OPFS API that make it actually usable now. Now they even have the field-sizing CSS property [0], fixing imo the most glaring ommission from CSS: the inability to make text input boxes grow to fit the i…

I thought that was supposed to be fixed by contenteditable plaintext-only. Why was field sizing still necessary?

Re: CSS Grid Lanes

#108

Post by simondotau » Sat, Dec 20, 2025, 4:03 AM UTC

concinds wrote: post #90

simondotau wrote: post #81

Earlier quoted context omitted.

The web platform doesn’t need to move this fast. Google is, often unilaterally, pushing new features and declaring them standards. In my opinion, the web should not be changing so fast that a truly open source community project couldn’t keep up. I don’t like how the web has become reliant on the largesse of billion dollar corporations. I recognise that this is a controversial take, but in my opinion what Google is do…

I know it's fashionable to forcefully shove the same pet peeves about Chromium into any topic even loosely related, but here I'm talking about Safari webcompat fixes, bug fixes, and improvements having very long delays between being written and landing in customers' hands. I would make the same argument if Chrome never existed. Thank you for presenting the 10,001st reissue of this "controversial take".

The behaviour of entities that WebKit is ostensibly told to be compatible with isn't a "loosely related" topic, it's precisely on-point. It's certainly no less on-point than nebulous criticisms of Apple for assumed NIH syndrome or marketing priorities. You criticise Apple for not having a rapid release schedule; I am criticising the very notion of rapid release schedules (other than security patches).

The web platform doesn't need to move so fast.

Re: CSS Grid Lanes

#109

Post by 65 » Sat, Dec 20, 2025, 4:36 AM UTC

culi wrote: post #27

Props to the Safari team. They surprised us all when they suddenly shot to the top of interop-2025 this October https://wpt.fyi/interop-2025

Safari became the new IE for a while, the amount of problems I've had with Safari CSS animations and SVGs is endless.

It's good they're trying to not make Safari suck as much.

Re: CSS Grid Lanes

#110

Post by 65 » Sat, Dec 20, 2025, 4:37 AM UTC

ray_v wrote: post #82

If I ever encounter, and need to read a webpage with arbitrarily sized and placed grids of text, please somebody just shoot me. https://webkit.org/wp-content/uploads/Grid-Lanes-newspaper-d...

NYTimes.com comes to mind...