W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2001

Response to T.V. Raman issue raised during second last call of UAAG 1.0

From: Ian Jacobs <ij@w3.org>
Date: Fri, 16 Mar 2001 22:59:50 -0500
Message-ID: <3AB2E136.6A95585D@w3.org>
To: tvraman@almaden.ibm.com
CC: w3c-wai-ua@w3.org
Raman,

Please find below a summary of how the UAWG addressed the
non-editorial last call issue (325) you raised;
please refer to the email source of the issues [0].

The complete second last call issues list [1] is available
online. The results of the UAWG's resolutions have been
incorporated into the 9 March 2001 draft of the document [2].

  NOTE: The issue titles relate to the 23 October 2000 last call
  draft [4]. In my comments below, checkpoint numbers, etc. have
  been updated to correspond to the 9 March 2001 draft.

Please indicate before 27 March whether you are satisfied with
the UAWG's resolutions, whether you wish the WG to carry forward
any objections to the Director as the document advances, or
whether you require further clarification or comment. If you do
not think you respond before 27 March, please let me know.  The
Director will appreciate a response whether you agree with the
disposition of comments or not. More information about the
process we are following is available in section 5.5.2 of the W3C
Process Document [3].

On behalf of the UAWG, thank you for your review and comments,

 - Ian

[0] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000OctDec/0216
[1] http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html
[2] http://www.w3.org/WAI/UA/WD-UAAG10-20010309/
[3] http://www.w3.org/Consortium/Process-20010208/tr.html#last-call
[4] http://www.w3.org/TR/2000/WD-UAAG10-20001023/

===============================================
The UAWG agreed with you:
===============================================

#325: Checkpoint 5.5: API notification of content change in one
viewport that causes change in another

  Comment: You requested the following functional requirement:

     "When user agents display content in multiple viewports --and the
     user's action in one view port causes the display in other view
     ports to be updated, the user agent should make such display
     update notifications available through standard APIs like the
     DOM/HTML event APIs."

   This is covered by our checkpoint 6.5:

     "6.5 Using standard APIs, provide programmatic alert of changes
     to content, user interface controls, selection, content focus,
     and user interface focus. [Priority 1]
        Note: For instance, when user interaction in one frame causes
        automatic changes to content in another, provide programmatic
        alert through standard APIs. Use the standard APIs required by
        the checkpoints of guideline 6."

-- 
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783
Received on Friday, 16 March 2001 22:59:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:38 GMT