home.social

#csswg — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #csswg, aggregated by home.social.

  1. Dearest #CSSWG friends, do you know if there has ever been a proposal for a ‘word’ unit, that’s as wide as the average width of all words? I really want this unit.

  2. at the @CSSWG.org (@CSSWG) F2F (face to face) meeting^1, hosted by @Apple.com (@Apple) in Cupertino. Not counting at #w3cTPAC, the prior #CSSWG F2F meeting I went to was 2.5y ago, also in Cupertino, and before that 2019 in SF. Good to see so many longterm colleagues in-person.

    #W3C #CSS #webStandards

    ^1 https://wiki.csswg.org/planning/cupertino-2026

  3. at the @CSSWG.org (@CSSWG) F2F (face to face) meeting^1, hosted by @Apple.com (@Apple) in Cupertino. Not counting at #w3cTPAC, the prior #CSSWG F2F meeting I went to was 2.5y ago, also in Cupertino, and before that 2019 in SF. Good to see so many longterm colleagues in-person.

    #W3C #CSS #webStandards

    ^1 https://wiki.csswg.org/planning/cupertino-2026

  4. at the @CSSWG.org (@CSSWG) F2F (face to face) meeting^1, hosted by @Apple.com (@Apple) in Cupertino. Not counting at #w3cTPAC, the prior #CSSWG F2F meeting I went to was 2.5y ago, also in Cupertino, and before that 2019 in SF. Good to see so many longterm colleagues in-person.

    #W3C #CSS #webStandards

    ^1 https://wiki.csswg.org/planning/cupertino-2026

  5. at the @CSSWG.org (@CSSWG) F2F (face to face) meeting^1, hosted by @Apple.com (@Apple) in Cupertino. Not counting at #w3cTPAC, the prior #CSSWG F2F meeting I went to was 2.5y ago, also in Cupertino, and before that 2019 in SF. Good to see so many longterm colleagues in-person.

    #W3C #CSS #webStandards

    ^1 https://wiki.csswg.org/planning/cupertino-2026

  6. at the @CSSWG.org (@CSSWG) F2F (face to face) meeting^1, hosted by @Apple.com (@Apple) in Cupertino. Not counting at #w3cTPAC, the prior #CSSWG F2F meeting I went to was 2.5y ago, also in Cupertino, and before that 2019 in SF. Good to see so many longterm colleagues in-person.

    #W3C #CSS #webStandards

    ^1 https://wiki.csswg.org/planning/cupertino-2026

  7. @csstricks

    Regarding there being no :closed besides :open, see also

    * :focus, and not focussed
    * :checked, and not checked

  8. New blog post: “Fit-to-Width Status Update: Prototype and Issues”

    blog.kizu.dev/text-fit-update/

    In which I present the current state of things and share links and descriptions of issues I opened in the CSS Working Group’s GitHub following the Chrome team’s feedback.

    #Accessibility #Typography #CSSWG #CSS

  9. That feeling when publishing 45 photos, where you write descriptions and alts for all of them, alongside editing and optimizing for publishing, haha, oof. :blobcatfearful:

    Anyways! I just published photos I took a bit more than a year ago in A Coruña, during our #CSSWG F2F outing: pixey.org/c/867866092272512417

  10. New blog post: “Fit-to-Width Discussions & Feedback”

    blog.kizu.dev/fit-to-width-dis

    A bit less than a year ago, I published my “Fit-to-Width Text: A New Technique” article. Since then, CSSWG resolved to start working on it, and, following this, two things happened: a discussion of its potential accessibility issues, and an intent to prototype it from Google.

    I have some thoughts, feedback, and ideas about both of these, so here is a post!

    #Accessibility #CSSWG #Typography #CSS

  11. OK, #CSSWG folks, whose brilliant idea was it to make auto-generated heading IDs for anchor links in the CSS spec end with ① or ② or ⑤ characters (for the 1st, 2nd, or 5th heading in a section without an otherwise specified ID).

    Looks very cute in a URL bar, but gets copy & pasted as URL encoded character barf. And then there's the likely screen-reader mangling of special characters.

    This had better be for Editor's drafts only & prompt a warning to add custom IDs before publication.

    🤨

  12. Downside: missed plane BOS->SFO because wheelchair arrived too late.
    Upside:
    chase.com/travel/guide/experie

    (will still make first day of #csswg meeting tomorrow)

  13. A reminder that #CSSnesting is still a working draft in the #W3C under the #CSSWG. Please mind #webcompat when using this relatively new feature. IOW, don't make your #CSS break because you assumed everyone right now is using the latest version of #Chrome / #Chromium, #Firefox, #Safari, or #Edge. They might not even be using a mainstream #browser to visit your website (I am using #PaleMoon for example)... ​:seija_coffee:​

    RE:
    https://c.im/users/youronlyone/statuses/111884225846166170