Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CSS Grid Lanes

webkit.org

Post reply on HN
Print view View original

231–237 of 237 posts

Re: CSS Grid Lanes

#231

Post by simondotau »

saagarjha wrote: post #229
simondotau wrote: post #176

Earlier quoted context omitted.

Because such bugs were predominantly associated with then-new platform features. As a web developer myself, I appreciate the frustration with Safari's flexbox bugs of a decade ago and viewport bugs more recently. I also remember being endlessly frustrated by Chrome bugs too, like maddening scroll anchoring behaviours, subpixel rounding inconsistencies, and position:fixed bugs which were broken for so long than the bu…

I'm not saying that other browsers don't have bugs. This thread is about how Safari doesn't fix them for a long time because it ships slowly.

You are assuming that Safari didn’t fix bugs for a long time because it “ships slowly.” Maybe some bugs are just complicated and take time to fix. It took Google years to fix the bugs I mentioned earlier (and many others) despite having the largest budget of any browser project and a VERY rapid release cadence.

Re: CSS Grid Lanes

#232

Post by Doxin »

dylan604 wrote: post #34
ThatMedicIsASpy wrote: post #6

I've run the masonry layout (for my personal bookmark website) ever since I've found it in the browser settings. grid-template-rows: masonry; is going to be outdated then?

I still prefer the layout look from something like justifiedGallery.js where the heights of each row are the same. Actual masonry with stacking stones would never stack directly on top of each other like this. Calling it masonry just feels unnatural as anything stacked like that would easily be knocked over. "Lanes" is definitely more appropriately named than "masonry". The layout look of a justifiedGallery would be…

One hack to almost get a justified gallery like that with no javascript is to lay them out with flexbox, setting their width to a percentage or vw value which your backend calculates based on image aspect ratio and desired image height, use flex-grow to stretch them to fill remaining space, and then using background-position: cover to make the images fit the slightly wrong aspect ratio containers.

This will of course slightly crop all your images to make it fit, but in practice as long as you keep your image aspect ratios reasonable and the images small enough on the page it's really quite subtle.

I had hoped that this feature would provide for masonry like that, but one has to make do.

Re: CSS Grid Lanes

#233

Post by dormento »

selfmodruntime wrote: post #153
rahkiin wrote: post #149

Earlier quoted context omitted.

Have you considered using tables? It is funny how we keep asking more and more and more even though we already have it so much better than before. Can we never be happy with what we have?

> It is funny how we keep asking more and more and more even though we already have it so much better than before. I've been developing web stuff for 15 years now and sometimes I can't believe comments like these. We didn't have it "so much better before". CSS sucked hard and getting things right for three devices was an incredible pain in the ass. Tables have semantic meaning. They don't support fractional units. Re…

> we already have it so much better than before

They meant now. "we have it so much better than how it used to be."

Re: CSS Grid Lanes

#234

Post by saagarjha »

simondotau wrote: post #231
saagarjha wrote: post #229

Earlier quoted context omitted.

I'm not saying that other browsers don't have bugs. This thread is about how Safari doesn't fix them for a long time because it ships slowly.

You are assuming that Safari didn’t fix bugs for a long time because it “ships slowly.” Maybe some bugs are just complicated and take time to fix. It took Google years to fix the bugs I mentioned earlier (and many others) despite having the largest budget of any browser project and a VERY rapid release cadence.

No a lot of them are pretty straightforward, this is why I’m upset. I’m talking about, like, “SVGs with this feature don’t render correctly due to an oversight in size calculation” not “can you please implement WebGPU in the next release cycle”.

Re: CSS Grid Lanes

#235

Post by ksec »

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

Nice Chart. This along with Interop 2024 actually tacks well what I thought was major improvements. I first noticed it was Safari 18 and Safari 18.2, and then Safari 26 and now 26.2 where sites that dont used to work well are now all working. To the point for as long as Safari 26.2 has released I dont remember I had to switch to Chrome or Firefox to check. Where previously I do it at least monthly or quarterly.

Hopefully they will make Safari smoother and faster with Multi Tabs in future release. There are lots of multi tab feature they could copy from Firefox.

Re: CSS Grid Lanes

#236

Post by ksec »

Unai wrote: post #163
65 wrote: post #109

Earlier quoted context omitted.

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.

Safari is still the new IE. Well, not really "new", it has been IE all along. It's the only non-evergreen browser that remains, and I don't get why this isn't mentioned every time Safari is brought up. All of their spec implementations are meaningless when the only version that matters is the one forever stuck in whichever oldest iPhone n% of people still use. Caniuse is pointless, their new "baseline" score is point…

iPhone or iOS has the highest upgrade percentage of OS. ~85%+ are on iOS 18 or higher. Liquid Glass iOS is the first time update has been slower. But Apple generally achieve near or over 80% of latest iOS by end of its cycle i.e coming August / September.

One could argue Safari on iOS being like macOS where it could be updated standalone, but current rate isn't too bad.

Re: CSS Grid Lanes

#237

Post by 47282847 »

snackbroken wrote: post #145
satvikpendem wrote: post #138

Earlier quoted context omitted.

This is so funny that I'm not even sure what to say. You can ask your exact questions about a newspaper but somehow 99% of people manage to read them just fine. I think it's just a you problem that you are looking for an exact algorithm on how to scan a page with multiple sizes of content; in reality, people just look over it all and keep track of what they have or haven't looked at all in their heads.

In a newspaper the answer is simple. You linearly scan the leftmost column to the bottom of the page, then the next column, then the next, and so on until you get to the end of the page. At no point do you ever need to keep track of anything other than "this is how far I've gotten" to make sure you haven't missed anything. Columnar layout make sense in newspapers because both axes are fixed in size, so all you ever d…

> In a newspaper the answer is simple. You linearly scan the leftmost column to the bottom of the page […]

Is this really how you think people read newspapers?

Post reply on HN