IMHO the most effective leaders in web standards are the best “centrists” we’ve got. The dialectics of stability and progress are difficult. Looking at you @w3c 🙌.
@mmatuzo Just letting you know the TIL#12 on your website isn't limited to Firefox or block-level behavior. Chrome also supports focus of user scrollable containers. Scroll containers just require a block formatting context, but can be inline. https://t.co/2vN64HySpi
@micahgodbolt Not exactly proud of this not mobile first chunk in my project starter...
@media screen and (max-width: 320px) {
html { font-size: 5vw }
}
But I've had it force my hand to create accessible layout down to 320px for years. FTMP 320px wide is a decent metric for accessibility.
@jaffathecake@rikschennink I can't imagine rubberbanding, the elastic effect, would not be present with their recent efforts in https://t.co/TlOth7wYaM, where overscroll-behavior has an initial value of auto.
@bdc And if you want to respect the internal and subsequent flow of content, you could change to using cacl() maths padding/margin instead of height, like this utility.
https://t.co/OwJOfZg447
@rachelandrew I recently updated your mdn writings on the inset shorthand to communicate physical mapping, instead of logical. Please feel free to tweak any of my changes if they can be improved or were incorrect. https://t.co/6oGZJaOuBJ https://t.co/PewX5FexrZ
@MagalieLinda @Real_CSS_Tricks It's for things like on-screen keyboards that can obscure the viewport while simply manipulating the visual viewport, to allow positioning part of your UI inside.
@anatudor As @tabatkins points out... "env() also should be usable in further contexts outside of properties on elements, such as in MQs" https://t.co/zR2osJ9leL