Dirk Fieldhouse wrote: > On 18/03/2021 23:42, Jonathan N. Little wrote: >> Dirk Fieldhouse wrote: >>> On 18/03/2021 14:23, Jonathan N. Little wrote: >> ...> mike wrote: >>>> or more modern: >>>> >>>> <a href="#to_anchor">To Anchor</a> >>>> >>>> <span id="to_anchor">All browsers will find me too</span> >>> >>> Are you sure? >> >> Yep, now I am. Open in Firefox and the TOC works. Disable JavaScript and >> reload and TOC and it no longer works in Firefox. Didn't bother to debug >> what the exact issue with SM was. >>...> > > There's a big difference between links that work out of the box (<a > href> -> <a name/id>) and scripted links. With the right (ie, very > wrong) scripting, any element can be made a link or a target: that's how > you break the web. > > The links work for me in SM2.53.6 with JavaScript enabled. However I > have the GitHub WebComponents extension installed, as anyone who needs > to use GitHub should: <https://github.com/JustOff/github-wc-polyfill>. > Maybe that makes the difference.
Absolutely. That is like the Angular shim files to add support for IE8 and lower for missing JS support. > > Off-topic: shouldn't that extension be built into SM for all sites? No, SM should be upgraded, but because of its legacy framework not only will upgrade break extension support but require a major rewrite of the codebase. A lot to ask of the volunteer developers. > That the site's links may work partially under some circumstances > doesn't affect the main issue which is that the links are incorrect and > the site should fix them. Similar to Eric Morecambe's musical notes, the > link elements have all the right attributes but the wrong values. BTW: Is anyone else getting those 'NameSilo Abuse Team' auto-replies lately when posting here? -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
