Live data from Hacker News

CSS Grid Lanes

webkit.org

221–230 of 237 posts

Re: CSS Grid Lanes

#221
post #216

Earlier quoted context omitted.

I get what you're saying but making interminable arguments and keeping the "debate" going is a tactic. There's that CIA sabotage manual with the section about meetings and conferences, it can feel like that. The duration of these debates aren't usually measured in hours, days, or weeks, but years. And the people who dragging them on and staying in the fights are employed full-time to do exactly that. It got to the po…

This feels very much tinfoil. There’s no incentive to the companies or the employees to draw out the discussion, especially over something so trivial. It’s much more preferable to try and speed through things to get things done in a time frame that can be adopted. And regardless, if you don’t feel it’s worth your time, then why cast aspersions that it was something clandestine and intentionally hidden? You could have…

Eh, you’re trying to put words in my mouth.

I didn’t ascribe a motive to anyone. Their reasons are their own and it only makes sense that the people who stay in these fights do it because it’s part of their jobs.

There are people who, for whatever reason, keep debates going over small points of disagreement and prevent issues from being settled. Sometimes for years. Right?

The older I get, the more likely I am to recognize and route around or ignore interminable debates. Especially if it’s not for a company, project, or initiative under my direct control.

Remember, the question at the top of this thread was essentially “What happened to ‘masonry’?” Well, there were quibbles over the descriptors.

I don’t care about quibbles. “masonry”, “grid-lanes”, “grid-masonry”, pick one, they’re equivalent. I don’t like it when quibbles block progress.

Sometimes people and companies do want to block things. You’d have to ask them why. Like I said earlier:

> I don't have an incentive to build consensus within a group of people who fundamentally disagree that the thing I need should exist.

Pick your battles… Actually, no, it’s usually better to ignore the fights and just get what you need to get done so you can move on.

Re: CSS Grid Lanes

#222
post #54

Earlier quoted context omitted.

I've done that for desktop apps before. You have to be careful with the effects of sub-pixel rendering and whatnot if your math is continuous, but it's a viable path that I quite like.

Don't use continuous math in either a design system nor a constraint solver that you expect random developers to use. Either case will only lead to problems.

I largely agree, but there's a little nuance insofar as "interior-point" methods are very powerful. You can go a long way by encoding your goals as error functions and letting a gradient-based optimizer do the rest.

Re: CSS Grid Lanes

#223

Earlier quoted context omitted.

Safari got a big update last week.

Safari in general got an update, or Safari on only the devices Apple deems worthy? Usually Apple limits Safari updates to new phones.

Do you consider six-year-old phones new? What about seven-year-old Macs?

Re: CSS Grid Lanes

#224
post #144

Earlier quoted context omitted.

Here's a comparison including the big 3, ladybird, servo, and flow https://wpt.fyi/results/?label=master&product=chrome&product... To answer your question, yes. Apple requires 80% test passage of all the tests on web-platforms-test in order to be considered as a valid browser for iOS so they specifically targeted this suite to reach that milestone It's a pretty silly requirement because wpt is not really meant to be…

I thought that no other browser engine could be provided on iOS. so no ladybird's engine, no servo, no gecko, no blink, only webkit

that was true until a few months ago due to a ruling in the EU. It's still currently the case that only WebKit can run on iOS but they're gearing up to change that

Re: CSS Grid Lanes

#225
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.

The only people who think Safari is the new IE are people who weren’t around for IE.

it's also not possible for Safari to be the new IE because they don't have 95% marketshare. And IE's unique problem was that they pushed features that only they supported. Safari's problem is it doesn't support certain features

Also the thing is that there are plenty of features supported by Safari and Firefox that Chrome is slacking on. Nobody every complains about those features though because nobody would try to use a feature not supported by Chrome in the first place

Re: CSS Grid Lanes

#226

Earlier quoted context omitted.

Safari in general got an update, or Safari on only the devices Apple deems worthy? Usually Apple limits Safari updates to new phones.

Do you consider six-year-old phones new? What about seven-year-old Macs?

I think the iPhone X is the newest model that is no longer receiving iOS updates. That came out in 2017. So 8 years ago

Re: CSS Grid Lanes

#227
post #2

This is exciting to see! I just used Masonry for a project this past week. While it works quite well and is pretty performant, it is pretty hacky using absolute positioning, wanting to know the aspect ratios of objects beforehand for smoother layout, and having to recalculate everything on resize. I'm looking forward to having a generally available native option one of these days.

There is ways of create a basic masonery layouts using only pure CSS grid. But dependes on the use case. Take this example where are mixed cards without images, only text, and with images plus text.

https://codepen.io/zardoz89/pen/KKVEGbw

Re: CSS Grid Lanes

#228

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?

The following should be compatible with both approaches:

    .masonry {
      display: grid;
      display: grid-lanes;
      grid-template-columns: repeat(auto-fill, minmax(180px, 1fr));
      grid-template-rows: masonry;
    }
Firefox and browsers supporting the old syntax will ignore the `display: grid-lanes` as it doesn't recognize it and fall back to the grid+masonry.

Browsers supporting the new syntax will override the `display: grid` with `display: grid-lanes` and ignore the `grid-template-rows: masonry` syntax.

Re: CSS Grid Lanes

#229

Earlier quoted context omitted.

Why do you keep conflating bug fixes with new platform features?

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.

Re: CSS Grid Lanes

#230

I think Apple should make Safari stable downloadable option for all platforms.

This might actually happen indirectly. Kagi’s new browser uses WebKit. macOS only now, but eventually it’ll come to windows

I have been using Kagi Orion on macOS and iPhone, so far so good.
Post reply on HN