181–190 of 234 posts
If it’s already awesome for you, please just give us display:constraints and fiddle with these boxes and grids as much as you want.
Can't believe paged media isn't really supported yet. Trying to do anything like line numbers for legal documents or page numbers is an absolute nightmare.
Page media has been supported for decades. Line numbers aren’t strictly related to page media. It’s hard to complain about the lack of in-depth support for a media that isn’t meant to display “the web”. I do agree that it could be better. They have been adding print-related features though, at least I remember some in CSS3. CSS Colors Level 4 includes cmyk functions.
Feels like we’re stuck in a “yes, it meant to be a universal platform” / “no, it meant to be a document viewer” loop.
Earlier quoted context omitted.
div { width: 640px; aspect-ratio: 16 / 9; }
> But with Chrome and Firefox supporting it behind an experimental flag So basically not supported, and you have to go back to div hell. There should be some future.js file that you can import to make all this stuff just work in older browsers.
I've been using if for months with no issues in cross-browser testing, and I haven't enabled any experimental flags.
Earlier quoted context omitted.
Yes you can https://css-tricks.com/almanac/properties/a/aspect-ratio/
Experimental on Safari, so it's unusable of you have a real world project.
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.
It's so interesting, these waves of CSS improvements. Before the flexbox/grid arrival, there were years of near-zero progress. The flexbox/grid release, uniquely coordinated across browsers (for once), was an excellent milestone, but not really a movement. These last 2 years though feel almost like a revolution in comparison to CSS's history. Somebody is pushing very hard. These are some very serious improvements tha…
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.
It's so interesting, these waves of CSS improvements. Before the flexbox/grid arrival, there were years of near-zero progress. The flexbox/grid release, uniquely coordinated across browsers (for once), was an excellent milestone, but not really a movement. These last 2 years though feel almost like a revolution in comparison to CSS's history. Somebody is pushing very hard. These are some very serious improvements tha…
I owe my professional career development to a lot of awesome people whom I met on the Internet and helped me at each turn, without asking for nothing in return.
Earlier quoted context omitted.
flex is ok, and actually fills a need, but can it be used to make e.g. a chat layout? i don't agree btw. grid is voodoo declarations that is worse than tables. pretty much need to stackoverflow to do anything
>but can it be used to make e.g. a chat layout? I don't see why not.
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.