Andy Kirkwood | MOTIVE wrote:
I have come across a couple of instances of this where headings have
been enclosed in an anchor, i.e.
a name=anchor id=anchorh1Heading text/h1/a
This causes the text colour of the heading to change when moused-over
(although not a link). From an interface
David R wrote:
Andy Kirkwood | MOTIVE wrote:
I have come across a couple of instances of this where headings have
been enclosed in an anchor, i.e.
a name=anchor id=anchorh1Heading text/h1/a
This causes the text colour of the heading to change when moused-over
(although not a link). From an
h2a name= id=/aSome heading/h2
Or drop the anchor tag altogether. What is the browser compatibility of
this:
a href=#someIdOnThePageGo to Some ID/a
...
h2 id=someIdOnThePageSome ID/h2
My initial tests show great support. Anyone know better?
--
Ben Curtis
Ben Curtis wrote:
Or drop the anchor tag altogether. What is the browser compatibility of
this:
a href=#someIdOnThePageGo to Some ID/a
...
h2 id=someIdOnThePageSome ID/h2
My initial tests show great support. Anyone know better?
Generation 4 and below browsers don't play ball with it, and
Ben Curtis wrote, On 20.01.2005 23:58:
Or drop the anchor tag altogether. What is the browser compatibility of
this:
a href=#someIdOnThePageGo to Some ID/a
...
h2 id=someIdOnThePageSome ID/h2
My initial tests show great support. Anyone know better?
I've been told, that
Can anyone clarify?
Me not :) However I'd use construction like
...
h1 id=tocTable of contents/h1
...
and you're done.
--
Jan Brasna :: alphanumeric.cz | webcore.cz | designlab.cz | janbrasna.com
Stop IE! - http://www.stopie.com/ | http://browsehappy.com/
Empty link elements are not good (as Patrick pointed out)but what about
named anchors (destination anchors)?
They are obsolete. Refer to any id instead.
Is there any reason why they should not be empty?
I wouldn't be surprised if it was because of a bug in Netscape4.
--
regards, Kornel Lesiski
Focas, Grant wrote:
Empty link elements are not good (as Patrick pointed out)but what
about named anchors (destination anchors)? Is there any reason why
they should not be empty?
I'm typically using anchors like this one:
a id=item_1 name=item_1/a, and can't see the need to fill them.
As Kornel
Title: Re: [WSG] empty named anchors
One reason why you might not want to have content inside of an
anchor would be because of the implementation of stylesheets (or more
accurately how style rules have been specified).
For example if a hover rule is written for to the a
element
