This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10511 - [scroll] fragment identifier algo should use scroll element into view
Summary: [scroll] fragment identifier algo should use scroll element into view
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on: 10533
Blocks:
  Show dependency tree / graph
 
Reported: 2010-08-30 17:10 UTC by Anne
Modified: 2010-10-13 20:19 UTC (History)
5 users (show)

See Also:

Attachments

Description Anne 2010-08-30 17:10:44 UTC 
http://dev.w3.org/csswg/cssom-view/#scroll-an-element-into-view should be used by the fragment identifier stuff, I think.
Comment 1 Boris Zbarsky 2010-08-30 17:29:17 UTC 
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.
Comment 2 Anne 2010-08-31 05:43:19 UTC 
The algorithm is blocking on cross-origin at the moment.
Comment 3 Ian 'Hixie' Hickson 2010-09-25 18:16:34 UTC 
Why shouldn't this be left up to the browser? The CSSOM algorithm seems to be media-specific, too.
Comment 4 Anne 2010-09-26 09:33:28 UTC 
I think visual user agents should do the same thing. And should be equally protected from the privacy issue.
Comment 5 Ian 'Hixie' Hickson 2010-09-29 07:46:07 UTC 
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.
Comment 6 Anne 2010-09-29 08:14:35 UTC 
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.
Comment 7 Ian 'Hixie' Hickson 2010-09-30 19:44:17 UTC 
Let me know what you decide to do and I'll fix this bug and 10533 accordingly.
Comment 8 Ian 'Hixie' Hickson 2010-10-13 20:19:51 UTC 
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