{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreih74d5xuvpxkhmpzxbno5bklax4dusdr4gik6fwegg2khd2lr2knm",
    "uri": "at://did:plc:6zlrzzlm3scek6n2lrpjdxrm/app.bsky.feed.post/3mnhylcne5e62"
  },
  "path": "/notes/2026-06-03-aa",
  "publishedAt": "2026-06-03T00:23:00.000Z",
  "site": "https://muan.co",
  "tags": [
    "Technology",
    "headingoffset is now in Firefox Nightly!",
    "https://github.com/whatwg/html/pull/3499#issuecomment-544745912",
    "https://github.com/whatwg/html/issues/5033",
    "Like",
    "(Backed by OpenHeart protocol)"
  ],
  "textContent": "headingoffset is now in Firefox Nightly!\n\nThis one is up there as the top 3 most challenging proposals I’ve made to standards due to social/politically/legacy baggage.\n\nThis is something that anyone who’s battled with user generated content heading structure and the confusion around `<section>` spec and the non-existent HTML5 content outline algorithm, would have much to say about.\n\nStart: https://github.com/whatwg/html/pull/3499#issuecomment-544745912 → https://github.com/whatwg/html/issues/5033\n\nOn another, more trying proposal I made, a respected standards person commented that “your problem is that you only think about your own use case”—the use case I have with building github.com. I remember feeling very hurt. Part because it is true that I don’t have the capacity to imagine uses cases outside of what my work demanded at the time, part because I felt like I failed to meet an expectation that is put upon people for attempting to engage in standards discussions.\n\nWHATWG claims that they want a diverse range of opinions, but often times tenured standard/browser engineers neglect to adjust their responses according to the different ways people contribute.\n\nThe same thing happened in Web Components spec meetings, in which I attended to provide input for developer experience and needs. I inadvertently got challenged on browser implementation limitations, and to that I could only shrug and shrink. I didn’t have the confidence to say “that’s not in my wheelhouse, I’m here to provide expert opinion as an application developer for github.com.” Instead I buckled up.\n\nHaving learned this and knowing what I know now, I would still rather not attempt these things again. Being able to stand firm on my position is one thing, but being unconstructively engaged with is another—One I would not tolerate anymore.\n\nWell, I guess this could have been a post. But a post is so much more serious and might get linked to and discussed much more than this stream of consciousness. I will just hide here.\n\n\nLike\n(Backed by OpenHeart protocol)",
  "title": "2026-06-03"
}