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? 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!
What seems to be the case is that in the endless rush to break the Web,
it was decided to deprecate <a name="target> for target anchors and
prefer (what TBL never wrote, but was invented with HTML 4.01) <a
id="target>. In other words, just about the first thing that anyone
learned about HTML anchors is now deprecated ...
The problem here is that the page has links but no matching anchors, or
vice versa.
As an example, take the heading "Introduction". Here's its ToC entry, an
unnumbered list item in a nested unnumbered list:
<li>
<a href="#Introduction">Introduction</a>
<ul>
...
</ul>
</li>
This would link to an anchor <a name="Introduction"> or <a
id="Introduction"> in the same document.
But this is the target heading:
<h1>
<a id="user-content-introduction" class="anchor"
href="#introduction" aria-hidden="true">
<svg class="octicon octicon-link" "...">...</svg>
</a>
<a name="user-content-introduction"></a>
<span>Introduction</span>
</h1>
If the Toc <a> element were:
<a href="#user-content-introduction" id="introduction"
name="introduction">Introduction</a>
and the elements in the heading were:
<a class="anchor" href="#introduction" aria-hidden="true">...
<a id="user-content-introduction" name="user-content-introduction">
<span>Introduction</span>
</a>
the page would work properly: clicking on the ToC "Introduction" takes
you to the heading, and clicking on the icon next to the "Introduction"
heading takes you back to the ToC entry. Maybe there's some site JS that
makes this vaguely better, but as I was testing HTML I didn't enable JS
for the page. When I did, I found that the ToC link worked, but the
reverse link didn't.
How this basic 1992 web functionality has been broken by some obscure
processing chain is a matter for the site owner, who may need to wrangle
GitHub's Wiki functionality harder (or bypass it). OP should try the New
Issue button here <https://github.com/SpiderLabs/ModSecurity/issues>.
/df
--
London
UK
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
