Dirk Fieldhouse wrote: > On 18/03/2021 14:23, Jonathan N. Little wrote: >> mike wrote: >>> in >>> https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual-%28v2.x%29 >>> >>> anchors do not work with SeaMonkey, i.e. clicking on a link does not >>> jump to the corresponding section. It works with Firefox, though. >> >> My guess is that it is using some specific JavaScript mechanism >> 'user-content-*' to act as a link that legacy SeaMonkey doesn't support >> or the JavaScript library used doesn't properly identify SeaMonkey to >> enable the function. Far better to just use tried and true link-anchor >> >> <a href="#to_anchor">To Anchor</a> >> ... >> <a name="to_anchor">All browsers will find me</a> >> >> 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. > This isn't in any spec I've seen, though it's trivial to implement in > JavaScript if you want a broken page. Also, keep quiet about it or > Google will try to add it to HTML5! I'm pretty sure they already know about it. There is a whole slew of these JS "frameworks" that complicate things. I can say SeaMonkey is having more and more issues with them. When developing in Angular SeaMonkey will now no longer load a node developer server. No I do not think this is great, but it is becoming more ubiquitous resulting more sites break in SeaMonkey. -- 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
