10511 2010-08-30 17:10:44 +0000 [scroll] fragment identifier algo should use scroll element into view 2010-10-13 20:19:51 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All RESOLVED FIXED P2 normal --- 10533 1 annevk ian bzbarsky ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 38218 0 annevk 2010-08-30 17:10:44 +0000 http://dev.w3.org/csswg/cssom-view/#scroll-an-element-into-view should be used by the fragment identifier stuff, I think. 38219 1 bzbarsky 2010-08-30 17:29:17 +0000 Note that there are some security/privacy issues here as regards scrolling up the parent iframe chain; Mozilla's been considering changing its behavior in various ways for this stuff. 38278 2 annevk 2010-08-31 05:43:19 +0000 The algorithm is blocking on cross-origin at the moment. 39378 3 ian 2010-09-25 18:16:34 +0000 Why shouldn't this be left up to the browser? The CSSOM algorithm seems to be media-specific, too. 39461 4 annevk 2010-09-26 09:33:28 +0000 I think visual user agents should do the same thing. And should be equally protected from the privacy issue. 39894 5 ian 2010-09-29 07:46:07 +0000 By media-specific, I mean that the algorithm in CSSOM makes no sense e.g. for audio browsers, unlike the one in the HTML spec which, while vague, does at least make sense for those media. 39910 6 annevk 2010-09-29 08:14:35 +0000 Right, I meant that HTML5 could keep the generic stuff but defer for visual media. But maybe CSSOM View should take it all given that scrollIntoView() uses the same algorithm. 40279 7 ian 2010-09-30 19:44:17 +0000 Let me know what you decide to do and I'll fix this bug and 10533 accordingly. 41261 8 ian 2010-10-13 20:19:51 +0000 Checked in as WHATWG revision r5620. Check-in comment: Move scrollIntoView() to CSSOM View and update the other scroll algorithm to use the CSSOM View definition. http://html5.org/tools/web-apps-tracker?from=5619&to=5620 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 above Rationale: CSSOM View will be updated accordingly