So ... I think I have to recommend against using #Lit to build whole websites, because it doesn't seem to support fragment links (https://example/#this-is-the-fragment) well or at all. It's great at building discrete elements without user-addressable parts, but that's not enough for rendering the top level of a whole page.
Tell me I'm wrong at https://github.com/lit/lit/discussions/3524.
@jyasskin well that seems like a crazy shortcoming. Shocked that doesn't seem to have come up before and been addressed. I guess there's not a convenient way to have the fragment break out of the shadowDom or be exposed somehow?
@jyasskin complete guess but my only thought is that most of the folks using fragments like that are doing anchors in Markdown so it hasn't come up for web components?
@graynorton @jyasskin make sense. I was thinking more about this after my last post. Makes sense that it doesn't work and even more sense that it has come up before, even if there's no definitive resolution.
@graynorton @mcneely It's a #Lit issue because Lit is alone among the major frameworks in putting component content in #ShadowDOM. It's true that a fix probably needs shadow dom changes, but people using Lit need to know the uses that they're going to have to code manually, and it's Lit folks who have the most expertise to use when pushing for these #WebStandards changes.
@mcneely It could be that people writing client-side renderers have already given up on fragments. But I was also surprised not to find any bugs about it.