ACTION-1427: Propose (at-risk) solution for selector references to be used in conjunction with IDREF

Propose (at-risk) solution for selector references to be used in conjunction with IDREF

State:
closed
Person:
James Craig
Due on:
April 28, 2014
Created on:
April 21, 2014
Associated Issue:
selector()
Related emails:
  1. FW: ARIA minutes - 5/19/14 (from bryan.garaventa@ssbbartgroup.com on 2014-05-20)
  2. RE: ARIA minutes - 5/19/14 (from bryan.garaventa@ssbbartgroup.com on 2014-05-20)
  3. ARIA minutes - 5/19/14 (from Andrew_Larkin@Comcast.com on 2014-05-19)

Related notes:

Also potential for repaint performance lag or whether changes to DOM elements in changed selectors may result in stale references in the accessibility tree. (e.g. Until recently, you couldn't even rely on [attr] selectors to update visible style; may have similar implications in the AX tree.)

James Craig, 21 Apr 2014, 18:03:55

I think this is too big for 1.1. Suggest punting to 2.0.

James Craig, 3 Aug 2014, 07:53:41

Punting to 2.0. Does not meet criteria for the 1.1 scope decided at TPAC 2014.

James Craig, 31 Oct 2014, 21:39:55

Display change log.


Joanmarie Diggs <jdiggs@igalia.com>, James Nurthen <nurthen@adobe.com>, Chairs, Michael Cooper <cooper@w3.org>, Ruoxi Ran <ran@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $