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

State of CSS

web.dev

Post reply on HN
Print view View original

211–220 of 234 posts

Re: State of CSS

#211

Post by jacobp100 »

5350-uiop-1130 wrote: post #199
soperj wrote: post #143

Earlier quoted context omitted.

It's so annoying to me that there's one browser that's holding everyone back. They also make it so that no one can use anything but their browser engine on mobile phones so they're harder to ignore.

also Safari dev tools are pure garbage, the worst i've used since IE 10. constantly crashes for no reason, refuses to select elements unless you close and re-open it, a weirdly stubborn cache, just so much worse than the chromium/firefox devtools. debugging in Safari is a major pain in the ass. and of all the browsers, Safari is the one that tends to render differently from others in a unwanted way. working with doze…

Safari dev tools has some good features Chrome doesn’t - like being able to override requests and responses in the network tab

Re: State of CSS

#212

Post by klysm »

conaclos wrote: post #197

I have the sentiment that CSS is now too bloated. It could be nice to obsolete some feature. A kind of edition could be pleasant : to get new features you have to opt out some old obsolete features. This also allows fixing known issues by breaking backward compatibility. For instance: `@edition(2023)` could make `box-sizing: border-box` the default

I wonder if editions wild simplify or complicate development. Since you still would have to support older editions it opens up interesting questions on code structure.

Re: State of CSS

#213

Post by woojoo666 »

dmitriid wrote: post #192
woojoo666 wrote: post #185

Earlier quoted context omitted.

Safari is so behind in terms of lack of support for free media formats/codecs like webm, webp, and av1. You can't even switch browsers to view them, since it's all webkit

> support for free media formats/codecs like webm, webp, and av1. You mean codecs developed exclusively by Google (often in rapid succession) and which Google aggressively pushes by abusing its dominant position https://www.protocol.com/youtube-tv-roku-issues

What's an alternative free media format? Not everything Google does is bad. In fact if you're against companies abusing their dominant position, Apple is perhaps one of the worst.

Worth noting that Safari is starting to roll out support for VP9, one of the formats by Google. Unfortunately this format is already rather outdated, and if Apple was going to support a free format now they should have gone for AV1. Which goes to show how slow they are

Re: State of CSS

#214

Post by moritzwarhier »

lyptt wrote: post #174

I'd love to see something like constraint layouts in pure CSS. It's an incredibly powerful tool when building user interfaces. I was really excited to see GSS ( http://gss.github.io ), however at the time it was far too slow to be usable in real projects.

That's the argument for container queries, in my view.

I imagine container queries will totally change the way I write CSS as soon they are broadly supported.

Of course this would not make for a truly constrained-based layout definition. But it would at least make working this way somewhat possible.

The example where flex-directon is switched using a container query is spot-on. That's exactly ly what I sometimes miss being able to do in HTML+CSS.

Apparently there is a JS polyfill (awesome given the problem) but I haven't tried it and I assume the performance implications are bad.

Re: State of CSS

#215

Post by alwillis »

woojoo666 wrote: post #185
dmitriid wrote: post #146

Earlier quoted context omitted.

When it comes to CSS Safari is rarely behind, and often ahead. When it comes to Chrome-only non-standards Safari is right where it needs to be: not implementing this bullshit.

Safari is so behind in terms of lack of support for free media formats/codecs like webm, webp, and av1. You can't even switch browsers to view them, since it's all webkit

Safari is so behind in terms of lack of support for free media formats/codecs like webm, webp, and av1

Both WebM [1] and WebP [2] have been supported by Safari for nearly two years now.

WebKit added support for AVIF (essentially the single-frame version of AV1) back in September [3]; AV1 is expected during the iOS 16/macOS Ventura release cycle.

[1]: https://webkit.org/blog/11648/new-webkit-features-in-safari-...

[2]: https://webkit.org/blog/11340/new-webkit-features-in-safari-...

[3]: https://webkit.org/blog/13152/webkit-features-in-safari-16-0...

Re: State of CSS

#216

Post by alwillis »

easrng wrote: post #159
lbotos wrote: post #67

Earlier quoted context omitted.

See my reply below: https://news.ycombinator.com/item?id=33289468 If you were able to style the element with "classic" CSS primitives like border/background/color would that not have also solved the problem without introducing new syntax with new quirks?

I've done this before. The problem is a lot of elements will change to a different (standard?) appearance when you add styles like that, so you'd need to recreate the original look if you wanted to just change the color. Also, each browser has different psuedoelements so you have to support firefox and webkit separately, which is made worse by the fact that webkit doesn't support targeting multiple elements with your…

For what it’s worth, having forms work the same across browsers is something Apple, Google and Mozilla are working on for Interop 2022: https://wpt.fyi/interop-2022

Re: State of CSS

#217

Post by pers0n »

#1 thing I’d like to see is to be able to set a baseline for typography using native css with calcium and other tricks

Re: State of CSS

#218

Post by lenkite »

dmitriid wrote: post #146
soperj wrote: post #143

Earlier quoted context omitted.

It's so annoying to me that there's one browser that's holding everyone back. They also make it so that no one can use anything but their browser engine on mobile phones so they're harder to ignore.

When it comes to CSS Safari is rarely behind, and often ahead. When it comes to Chrome-only non-standards Safari is right where it needs to be: not implementing this bullshit.

I just wish Safari was available on other operating systems - windows, android, etc.

Re: State of CSS

#219

Post by Macha »

hot_gril wrote: post #164
reaperducer wrote: post #49

Earlier quoted context omitted.

I'm always excited by newer features to CSS that make older JS-only methods obsolete. I wonder if it's just about how some people's brains are wired. I grok CSS. I won't claim to know everything about it, but I'd say I'm 90% proficient and prefer it to JavaScript. But I think this is because JavaScript somehow never fully made sense to me. I can read it and figure out what it's doing, but it was never intuitive to me…

I don't understand either one. I use React (while technically pure JS, I assume this isn't what you mean) and calculate most of the sizes manually, just passing width and height as props into my elements. People tell me that's dumb, but it's always worked, and I don't have to keep up with this topic of CSS that doesn't really interest me. I've tried the "correct" flexbox way too, and it wasn't easier. One particular…

For img you set one of width/height attributes on the image or the aspect ratio CSS property (for page stability during early loading, actual dimensions are preferred), then max-width: 100%; height: auto to scale according to horizontal space, or max-height:100%; width:auto to scale according to vertical space.

The additional complexity of images is that you nearly always want to maintain the aspect ratio, whereas a p or a div can be a radically different shape depending on the amount of content and viewport size and only have issues at the extremes (like very long lines at 4k@1x, or one word per line at high zoom)

Re: State of CSS

#220

Post by Macha »

andrewmcwatters wrote: post #145
asiachick wrote: post #120

Earlier quoted context omitted.

IIRC the way someone reimplemented flexbox was to take the layout tests and iterate until their implementation passed. https://yogalayout.com/

There may be layout tests for flexbox (I haven't looked into them, because I don't care about them as much as normal flow) but there are basically no layout tests for CSS 2.1 that aren't fully manual. So basically for 25 years, as far as I understand, no one said, hey given a set of known layout constraints and rasterization parameters, let's create automated tests. For 25 years. Maybe I'm wrong, but I keep looking f…

There was acid2, so merely "almost none" rather than actually none
Post reply on HN