4 ms·
vh was also invented to solve the height problem and it didnt. The current workaround still involves javascript! And dvw doesnt even solve the scrollbar probl
by seydor 4y ago
vh was also invented to solve the height problem and it didnt. The current workaround still involves javascript! And dvw doesnt even solve the scrollbar problems so , javascript again.
There s so much going wrong with CSS through the years (cough, grid) that one wonders if it's being deliberately sabotaged. But most likely it's suffering from FOMOitis where , every weekly design trend must make its way into CSS.
Or maybe at some point Chrome developers will get fed up and say f'it and invent a new simple pixel level language to do whatever you want.
- azangru 4y ago> (cough, grid) What's wrong with grid?
- seydor 4y agoi find it terrible design that breaks html as a language (that s meant to be readable). a bunch divs positioned arbitrarily via css is much less intuitive than <tables> where you can move blocks of markup to redesign geometrically . It's such a simpler mental model , and a set of <grid> elements would suffice. Changing layout with css grid involves changing multiple classes and is atrocious. Then there is the cryptic syntax where somehow "1 fraction" = "fill the rest of the space with it". I can hardly understand the motivation behind the grid design. Using tables is still much more pleasant, but modern browsers dislike table layouts and render them horribly.
- asddubs 4y agothe main problem with tables (besides render speed) is that it's very hard to prevent them being stretched wide by long contiguous words (like aaaaaaaaaaaaaaaaaa...) and images, and the usual ways to prevent those things don't work right in them. also there's no css rules for rowspan/colspan
- seydor 4y ago> don't work right in them. also there's no css rules for rowspan/colspan Yeah that's what i m talking about. Someone has been racist to tables
- Semaphor 4y agoI find it far easier to change things with grid than with tables. I think you might want to check named grid-templates if changing things currently requires changing classes.
- Shish2k 4y agoHow do you do responsive design when your layout is hard-coded as part of your document?
- seydor 4y agoThe column-span could be a css property. Still more readable
- azangru 4y ago> a bunch divs positioned arbitrarily via css is much less intuitive than <tables> where you can move blocks of markup to redesign geometrically <...> Using tables is still much more pleasant, but modern browsers dislike table layouts and render them horribly. With html being a semantic markup language, tables should appropriately be used for tabular data. Grids are addressing a layout concern, in which you want to position stuff on your page just so. With grids, you can easily change the arrangement of your elements within a grid at different screen sizes, or opt out of the grid altogether. With html table markup, that would not be not possible.
- mhoad 4y agoI’d argue that’s actually a decent description of what Flutter is.
- oefrha 4y ago> vh was also invented to solve the height problem and it didnt. The current workaround still involves javascript! Does it? `min-height: stretch` (expanded into `min-height: -webkit-fill-available` by autoprefixer) plus a `@supports (min-height:-moz-available)` workaround for FF seems to solve the problem, however inconvenient. That's what I've always used anyway. [1] https://caniuse.com/mdn-css_properties_min-height_stretch https://caniuse.com/mdn-css_properties_min-height_stretch