[whatwg] HTML5 Feedback: Section 3.5.3 Scrolling elements into view

[Bonner, Matt (IPG)]

Ian Hickson wrote:

> On Mon, 8 Oct 2007, Brad Fults wrote:
> >
> >   2. It may not be possible to align the top of the element 
> >      with the top of the viewport without scrolling past the 
> >      bottom of the document, so the "must" is unreasonable. 
> >      This contingency should be mentioned (scrolling past the
> >      bottom of the document is not, as far as I know, desired).
> 
> I don't understand what you mean. How can something in the document be
> further down than the bottom of the document?

I'm wondering if he was thinking about cases where the element is
shorter vertically than the viewport?  It might be worth clarifying
what happens in that case.  I assume the answer is "nothing"?

> > Secondly, with respect to this section as a whole, I see no description
> > of necessary behavior for horizontal scrolling. Surely this is an issue
> > that must be addressed, as it would be decidedly deficient if
> > scrollIntoView() only took vertical scrolling into account, leaving
> > horizontally overflown content still outside of the viewport after the
> > method's invocation.
> 
> Do UAs do any horizontal scrolling today? I've mentioned it, 
> but I'm not sure what to say really.

Well, it seems like you could offer instructions analagous to
the vertical case, substituting "left" and "right" for "top"
and "bottom", no?  That could imply a second argument to the
function...

Matt
--
Matt Bonner
Hewlett-Packard Company
 

> -----Original Message-----
> From: whatwg-bounces at lists.whatwg.org 
> [mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Ian Hickson
> Sent: Tuesday, June 03, 2008 4:33 AM
> To: Brad Fults
> Cc: WHAT-WG
> Subject: Re: [whatwg] HTML5 Feedback: Section 3.5.3 Scrolling 
> elements into view
> 
> On Mon, 8 Oct 2007, Brad Fults wrote:
> >
> > There are a couple of problems I have found in this section.
> >
> > "If it isn't possible to show the entire element in that 
> way, or if the
> > argument is omitted or is true, then the user agent must 
> instead simply
> > align the top of the element with the top of the viewport." [1]
> >
> > I have two issues with this text:
> >
> >   1. The word "simply" is rhetoric and doesn't seem reasonable or
> > useful in the context of this part of the specification.
> 
> Removed.
> 
> 
> >   2. It may not be possible to align the top of the element 
> with the top
> > of the viewport without scrolling past the bottom of the 
> document, so
> > the "must" is unreasonable. This contingency should be mentioned
> > (scrolling past the bottom of the document is not, as far as I know,
> > desired).
> 
> I don't understand what you mean. How can something in the document be
> further down than the bottom of the document?
> 
> 
> > Secondly, with respect to this section as a whole, I see no 
> description
> > of necessary behavior for horizontal scrolling. Surely this 
> is an issue
> > that must be addressed, as it would be decidedly deficient if
> > scrollIntoView() only took vertical scrolling into account, leaving
> > horizontally overflown content still outside of the 
> viewport after the
> > method's invocation.
> 
> Do UAs do any horizontal scrolling today? I've mentioned it, 
> but I'm not sure what to say really.
> 
> --
> Ian Hickson               U+1047E                
> )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   
> _\  ;`._ ,.
> Things that are impossible just take longer.   
> `._.-(,_..'--(,_..'`-.;.'
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4798 bytes
Desc: not available
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20080605/9f4ba5f7/attachment-0001.bin>