Re: [css-d] Browser don't catch named anchors if in fixed elements...

2005-09-06 Thread David Hucklesby
On Tue, 6 Sep 2005 11:30:02 -0700, Thierry Koblentz wrote: > > Using a DIV rather than an anchor may create problems with tabbing > navigation: > http://www.juicystudio.com/article/ie-keyboard-navigation.php > Wow! Thierry, reading that article makes my head hurt. Gez Lemon says: > I don't use na

Re: [css-d] Browser don't catch named anchors if in fixed elements...

2005-09-06 Thread Thierry Koblentz
> Modern browsers prefer you use "id" rather than "name". If you want to > target version 4 browsers, simply add an "id" attribute with the same > value as "name". Otherwise you may prefer to put the "id" into an > existing DIV or other element and get rid of the named anchor. It > works just as we

Re: [css-d] Browser don't catch named anchors if in fixed elements...

2005-09-06 Thread David Hucklesby
On Tue, 06 Sep 2005 17:31:02 +0200, Guillaume wrote: > > Seems the browsers ( Op, Saf, Ff on Mac ) don't catch named anchors > Hi Guillaume, Modern browsers prefer you use "id" rather than "name". If you want to target version 4 browsers, simply add an "id" attribute with the same value as "name".

Re: [css-d] Browser don't catch named anchors if in fixed elements...

2005-09-06 Thread Steve Clay
Tuesday, September 6, 2005, 11:31:02 AM, Guillaume wrote: > Seems the browsers ( Op, Saf, Ff on Mac ) don't catch named anchors if > placed inside position:fixed containers... Also scrolling areas with overflow:auto/scroll should scroll to make targeted anchors visible. The specs just don't say w