4 ms·
This is caused by using CSS grid with "minmax(auto, 57rem)" and an overflowing table. It can be fixed with adding "safe" to "justify-content: safe center" that
by uallo 4mo ago
This is caused by using CSS grid with "minmax(auto, 57rem)" and an overflowing table. It can be fixed with adding "safe" to "justify-content: safe center" that is defined on main.
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/justify-content#safe https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/P...
- ryandrake 4mo agoFunny how the problem itself is created by CSS, and the solution is "more CSS." On the other hand, bare HTML tends to be extremely accessible and lacks these kinds of basic problems with panning, zooming, and scrolling.
- bobthepanda 4mo agoCSS is this weird thing where it has dominance as a layout engine because it is so battle tested compared to a lot of other layout engines, but was clearly designed by a committee that could give a rat’s ass about how ergonomic it is to use. It took until 2023 to support nesting, something that was so obvious that preprocessors have had it since at least 2006.
- xigoi 4mo agoBare HTML is pretty bad for accessibility. For example, you get no maximum width, making websites painful to read in a wide window.
- mostlysimilar 4mo agoWindows are resizable. Built-in width selection!
- xigoi 4mo agoYou can’t set a different size per site. More width is better for sites that have sidebars and stuff.