3 ms·
> I'm looking at you Microsoft Github. Where don't anchors work when javascript is disabled? (With admittedly very brief testing just now, I couldn't find any
by gnomewascool 7y ago
> I'm looking at you Microsoft Github.
Where don't anchors work when javascript is disabled? (With admittedly very brief testing just now, I couldn't find any such cases.)
- superkuh 7y agoOn every single repo index page that has "anchors" that I've tried over the last year. The markdown is now interpreted different so anchors are class="anchor" and not real anchors. Maybe you didn't fully disable JS? Make sure JS is disabled before you load the page and you've cleared your cache (ctrl-f5 in FF-alikes). I just went to the most recent github tab in my browser session and found one instantly: https://github.com/quiet/quiet#dependencies https://github.com/quiet/quiet#dependencies
- kemayo 7y agoCan't say I've noticed it, but then I'm going around with Javascript enabled, so it's not like I would. That said, the github one is a sort of interesting case, insofar as they're doing it to avoid user-generated content clashing with their page-chrome ids... while still preserving a readable URI that matches what the content creator expects. Which doesn't seem like an unreasonable case, to me. You'll note that there is a real anchor on that link -- https://github.com/quiet/quiet#user-content-dependencies https://github.com/quiet/quiet#user-content-dependencies -- which works without Javascript. It's just rather inaccessible.
- gnomewascool 7y agoYou're right. I was wrong. Sorry! I had tested linking to specific comments in issue threads, which does work with JS disabled (unless I've completely messed up...), and assumed that linking to parts of documents, as less complex/application-y would obviously work, but as you've pointed out it doesn't. That's highly disappointing.