15526 2012-01-11 17:26:31 +0000 Nitpick / clarification request: Navigation to fragment identifier doesn't specify value of non-optional "align to top flag" "When the user agent is required to scroll to the fragment identifier, it must change the scrolling position of the document using 2012-02-07 00:41:41 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 62556 0 contributor 2012-01-11 17:26:31 +0000 Specification: http://dev.w3.org/html5/spec/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Nitpick / clarification request: Navigation to fragment identifier doesn't specify value of non-optional "align to top flag" "When the user agent is required to scroll to the fragment identifier, it must change the scrolling position of the document using the scroll an element into view algorithm defined in the CSSOM View specification, or perform some other action, such that the indicated part of the document is brought to the user's attention." [Section: 5.5.9 Navigating to a fragment identifier] I looked at the "scroll an element into view algorithm" in CSSOM View, and found you have to specify whether you want "align to top" (or the reverse - align to bottom). Looking at current behaviour, I think we want to specify "align to top" :). Note that this is the default for element.scrollIntoView(), but the named algorithm doesn't have a default. Ideally, this should be specified, or CSSOM View should be clarified so that the flag has a default value of "true". When I first looked at this, because of the way the algorithm is written, my impression was that the algorithm would default to "align to bottom" behaviour, which is the opposite of what we want. Posted from: 86.53.68.233 User agent: Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 63796 1 ian 2012-02-07 00:40:37 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 63798 2 contributor 2012-02-07 00:41:41 +0000 Checked in as WHATWG revision r6974. Check-in comment: Suggest scrolling to top. http://html5.org/tools/web-apps-tracker?from=6973&to=6974