W3C home > Mailing lists > Public > public-html-comments@w3.org > January 2009

Re: 9: fragment scrolling

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 16 Jan 2009 01:04:06 +0000 (UTC)
To: "Barclay, Daniel" <daniel@fgm.com>
Cc: public-html-comments@w3.org
Message-ID: <Pine.LNX.4.62.0901160100300.7181@hixie.dreamhostps.com>

On Fri, 11 Jul 2008, Barclay, Daniel wrote:
> Section 9 says:
>    CSS UAs in visual media must, when scrolling a page to a fragment identifier,
>    align the top of the viewport with the target element's top border edge.
> Isn't that wording a little over-constraining?
> For example, what if a user agent wants to show the user some context by 
> scrolling the identified fragment to slightly below the top of the 
> viewport in order to show a little of the content before the identified 
> fragment.  If the UA still showed the user the location of the 
> identifier fragment (e.g., by rendering in the left UI border an arrow 
> that pointed to the location within the viewport of the identified 
> fragment), wouldn't that satisfy the intent?

The entire rendering section is intended to be non-normative. (It's not 
written yet, so that isn't clearly stated.) The idea is to describe 
exactly what today's UAs do for existing features where there is interop, 
so that someone can develop a new browser relatively easily, with good 
confidence that what they implement will work with existing content.

Note that the actual requirements are much looser:


Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 16 January 2009 01:18:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:25 UTC