Jump to main content

Nicolas Hoizey

  • articles
  • billets
  • links
  • notes
  • talks
  • archives
  • about

Eric Bailey avatar Eric Bailey

display: contents considered harmful

  • Nicolas Hoizey
  • 25 May 2023
  • CSS, accessibility
  • 8 reactions
Screenshot of “display: contents considered harmful”

https://ericwbailey.website/published/display-contents-considered-harmful/

At this point, I don’t think we as an industry can use display: contents with confidence. Past actions are a good indicator of future behavior, and the road to hell is paved with good intentions.

8 reactions

5 likes

  1. 0gust1 avatar
  2. Noé avatar
  3. Anton 🇺🇦🇪🇺 avatar
  4. Tyler Sticka avatar
  5. kolya@social.cologne avatar

3 replies

  1. kolya@social.cologne avatar kolya@social.cologne
    @nhoizey @eric no explanation how display: contents breaks assistive tech (or how this is the fault of the spec and not the assistive tech), no explanation what the regressions did and why. however lots of lamenting and then this gem: "it is clear that most browser makers are untrustworthy". Seriously?
    • 3 June 2023, 09:11
    • Source
  2. kolya@social.cologne avatar kolya@social.cologne
    @nhoizey @eric display: contents has been a very helpful workaround for me on occasion, never a regular tool. and this article doesn't convince me - as it obviously tries to - to never use it again.
    • 3 June 2023, 09:14
    • Source
  3. Anton 🇺🇦🇪🇺 avatar Anton 🇺🇦🇪🇺
    @nhoizey @eric Isn't this what the Web Platform Tests were built to fix? Make a test for all the issues, and now browsers will be alerted every time they have a regression. It seems like they take WPT regressions seriously.
    • 3 June 2023, 09:28
    • Source
  • Older: Early Days Examples of View Transitions
  • Newer: My double standards about JS framework compilers

Related contents with similar topics

  1. screenshot of Pixels vs. Relative Units in CSS: why it’s still a big deal

    Kathleen McMahon avatar Kathleen McMahon

    Pixels vs. Relative Units in CSS: why it’s still a big deal

    • Nicolas Hoizey
    • 20 April 2023
    • accessibility, CSS, em, rem
    • 4 reactions

    Remember, users really do change their settings under the hood, and we should be maintaining users’ control over their own browsing experience. If…

  2. screenshot of The Surprising Truth About Pixels and Accessibility: should I use pixels or rems?

    Josh W. Comeau avatar Josh W. Comeau

    The Surprising Truth About Pixels and Accessibility: should I use pixels or rems?

    • Nicolas Hoizey
    • 20 May 2022
    • CSS, rem, accessibility

    Josh's attention to details in all his articles is awesome. Here, he's presenting evidences that the rem unit should be used for font sizes, media…

  3. screenshot of Inclusively Hiding & Styling Checkboxes and Radio Buttons

    Sara Soueidan

    Inclusively Hiding & Styling Checkboxes and Radio Buttons

    • Nicolas Hoizey
    • 24 June 2020
    • CSS, accessibility
    • 3 reactions

    Sara shows us how to properly use SVG and CSS to design beautiful, engaging and accessible checkboxes and radio button in her new very detailed article,…

  4. screenshot of Font sizing with rem could be avoided

    Harry Roberts avatar Harry Roberts

    Font sizing with rem could be avoided

    • Nicolas Hoizey
    • 20 February 2019
    • em, rem, 62.5%, accessibility, CSS

    I don't really agree with the simple statement made in the title of this article, as sizing fonts with rem is sometimes useful to escape the default…

  5. Gastero Prod 4, les standards et l'accessibilité

    • Nicolas Hoizey
    • 20 April 2004
    • SPIP, standards, accessibility, CSS

    L'accessibilité devient petit à petit incontournable. Outre ses avantages directs en terme d'élargissement d'audience des sites, elle a tendance dans…

If you want to share an error or suggest an enhancement of this content, please edit the source on GitHub.

© Nicolas Hoizey

Built with Eleventy