Skip to content

Commit

Permalink
[] (0) scrolling (not that this says much, but that's really UI stuff…
Browse files Browse the repository at this point in the history
… so let's keep out of the way)

git-svn-id: http://svn.whatwg.org/webapps@514 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jan 27, 2007
1 parent 69ed5b5 commit de5117e
Show file tree
Hide file tree
Showing 2 changed files with 24 additions and 19 deletions.
22 changes: 12 additions & 10 deletions index
Original file line number Diff line number Diff line change
Expand Up @@ -18333,8 +18333,8 @@ XXX selection ranges -->

<li>
<p>If the new resource is the same as the current resource, but a
fragment identifier has been specified, then <a href="#x" title="scroll
to fragment identifier">scroll the document to the specified element</a>
fragment identifier has been specified, then <span title="scroll to
fragment identifier">scroll the document to the specified element</span>
and abort these steps.

<li>
Expand Down Expand Up @@ -18641,15 +18641,17 @@ XXX selection ranges -->
<h4 id=scroll-to-fragid><span class=secno>4.1.5. </span>Scrolling to a
fragment identifier</h4>

<p class=big-issue><dfn id=x title="scroll to fragment
identifier">...</dfn> update scroll position, qv rendering section, update
history object
<p>When a user agent is supposed to scroll to a particular element, it may
change the scrolling position of the document as desired, or perform any
other relevant action.

<p class=big-issue>"In both cases, if the location before the method call
would differ from the location after the method only in terms of the
fragment identifier, then the user agent must use the same <code><a
href="#documentui">DocumentUI</a></code> object, updating only the scroll
position in the document's view(s) appropriately."
<p class=big-issue>how to get a "particular element" from a frag id --
id="", name="", XPointer, etc; missing IDs (e.g. the infamous "#top")

<p>Then, the user agent must <a href="#update">update the session history
with the new page</a>, where "the new page" has the same
<code>Document</code> as before, but potentially has a different scroll
position.

<h4 id=non-DOM-inline-content><span class=secno>4.1.6. </span>Displaying
inline content that doesn't have a DOM</h4>
Expand Down
21 changes: 12 additions & 9 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -16633,15 +16633,18 @@ XXX selection ranges -->

<h4 id="scroll-to-fragid">Scrolling to a fragment identifier</h4>

<p class="big-issue"><dfn title="scroll to fragment
identifier">...</dfn> update scroll position, qv rendering section,
update history object</p>

<p class="big-issue">"In both cases, if the location before the
method call would differ from the location after the method only in
terms of the fragment identifier, then the user agent must use the
same <code>DocumentUI</code> object, updating only the scroll
position in the document's view(s) appropriately."</p>
<p>When a user agent is supposed to scroll to a particular element,
it may change the scrolling position of the document as desired, or
perform any other relevant action.</p>

<p class="big-issue">how to get a "particular element" from a frag
id -- id="", name="", XPointer, etc; missing IDs (e.g. the infamous
"#top")</p>

<p>Then, the user agent must <span>update the session history with
the new page</span>, where "the new page" has the same
<code>Document</code> as before, but potentially has a different
scroll position.</p>


<h4 id="non-DOM-inline-content">Displaying inline content that doesn't have a DOM</h4>
Expand Down

0 comments on commit de5117e

Please sign in to comment.