[Bug 8715] Scrolling elements into view

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8715


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |NEEDSINFO




--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-02-17 22:19:55 ---
> The notion of a 'view' is relative in different modalities. Some users are
> sighted, some not. A sighted person may glance at a page and quickly understand
> context etc, a non-sighted person may need to be able to easily navigate to an
> area of the page, or quickly tab to various elements to be given this sense of
> context. Do you follow?

I am in fact quite well acquainted with matters of accessibility, yes.


> If so, there should be a way of supporting a non-visual mode of access (the
> spec currently refers to it as "media-specific manner most useful to the
> user"). I suggest the text needs to be more specific in /how/ to do this. In
> its simplest terms - this could be for example, a parent element in the DOM
> etc.

As far as I can tell, this is requesting some concrete examples of what
scrollIntoView() might do in browsers for different media. But if that's what
is being requested, then why is the spec not sufficient? The very *first* media
it talks about is speech browsers. It mentions these even before visual
(screen) browsers. The method is defined in terms that are completely
media-independent.

Maybe the bug report is only about the argument to the method? But in that case
I don't understand why anything needs to happen. Why would we want to apply a
visual attribute to a non-visual UA? I don't understand how the attribute would
even make sense in a braille or speech medium, for example.

What does "a parent element in the DOM" have to do with this?

I'm very confused as to what is being requested.

Could I ask for some sample text that you would want the spec to have that
would satisfy this bug report?


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: Did Not Understand Request
Change Description: no spec change
Rationale: see above


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 17 February 2010 22:19:56 UTC