Chronotope’s avatarChronotope’s Twitter Archive—№ 153,888

              1. I hate what browsers have done to the scroll bar, perfectly illustrated by this 2020 era CodePen that previously displayed a variety of scroll bar colors and widths and went from the version on the left to the modern browser version on the right.
                oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
            1. …in reply to @Chronotope
              I especially hate how browsers hide the scroll bar entirely on mobile devices. Horizontal scrollbars should be easy & straightforward to force into permanent visibility when the content is expected to make a scroll opportunity non-obvious yet... they do not.
          1. …in reply to @Chronotope
            The new scrollbar-width property (Firefox only), you'd think, would let you... you know... set the scrollbar width? But no, it's only options are auto and thin and as far as I can tell someone forgot horizontal scrollbars with height exist. developer.mozilla.org/en-US/docs/Web/CSS/CSS_Scrollbars
            OpenGraph image for developer.mozilla.org/en-US/docs/Web/CSS/CSS_Scrollbars
        1. …in reply to @Chronotope
          While we're here... also extremely frustrating that setting display: block on a table is understood and shown in a sane way in every browser but Safari.
      1. …in reply to @Chronotope
        Every other browser goes 'ah, yes, treat the table like it is contained inside a div' and Safari goes 'I know not of what you speak and I cannot and *will not* apply this display property'.
    1. …in reply to @Chronotope
      So now I'm going to have to write a markdown-it plugin I guess, just for Safari's sake.
  1. …in reply to @Chronotope
    But back to the original point: I don't understand the obsession with withholding developer control over the scroll bar. This should be an obvious feature for developer manipulation, as it's a vital part of interaction with your page.
    1. …in reply to @Chronotope
      And unequal rollout of a feature that alters content flow is a clear fingerprinting vector btw


Search tweets' text