4 ms·
It’s a hopelessly bad illustration of that. The web does a singularly excellent job of supporting varying viewport sizes out of the box, but this page actively
by chrismorgan 5y ago
It’s a hopelessly bad illustration of that.
The web does a singularly excellent job of supporting varying viewport sizes out of the box, but this page actively sabotaged that by claiming to support mobile:
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
While applying CSS rules that ruin it:
.article-card, article h1, article ul, article p, article ol {
width: 600px;
}
pre {
overflow-x: hidden;
}
These rules are obviously bad. width should be max-width, and, well, what would you expect to happen if you tell it to hide the overflow?
(It would have been OK even with these rules if the page hadn’t claimed to support mobile sizes, as the mobile browser would have rendered the page on a larger viewport and scaled it down, more or less.)
- tobr 5y agoYes, and this is exactly the type of problem you run into when your layout model is based on three-dozen-piled-layers-of-cruft.
- chrismorgan 5y agoShow me a layout system that doesn’t let you break things in this sort of way, and I’ll show you a useless layout system.