This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6883 - Transition after "Dynamic role changes are considered an error..."
Summary: Transition after "Dynamic role changes are considered an error..."
Status: RESOLVED FIXED
Alias: None
Product: ARIA
Classification: Unclassified
Component: Core AAM (show other bugs)
Version: 1.0
Hardware: PC All
: P1 normal
Target Milestone: ---
Assignee: Cynthia Shelly
QA Contact: ARIA UA Implementors
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-08 17:31 UTC by Andi Snow-Weaver
Modified: 2011-03-31 14:20 UTC (History)
0 users

See Also:


Attachments

Description Andi Snow-Weaver 2009-05-08 17:31:52 UTC
3.4 Role Mapping: Need transition after "Dynamic role changes are considered an error"
Comment 1 Andi Snow-Weaver 2009-06-08 21:46:39 UTC
Need help determining what these bullets are about since they seem to have nothing to do with role mapping:

    * Under MSAA/IAccessible2, the events are EVENT_OBJECT_HIDE and EVENT_OBJECT_SHOW, with EVENT_OBJECT_REORDER on the parent accessible object
    * Under ATK/AT-SPI, fire children-changed:remove followed by children-changed:add for the new object

Parking the code here for now:

<p class="todo">Todo: some sort of transition / explanation of what follows appears to be missing at this point.</p>
		<ul>
			<li>Under <abbr title="Microsoft Active Accessibility">MSAA</abbr>/IAccessible2, the events are <code class="api-event">EVENT_OBJECT_HIDE</code> and <code class="api-event">EVENT_OBJECT_SHOW</code>, with <code class="api-event">EVENT_OBJECT_REORDER</code> on the parent accessible  object</li>
			<li>Under <abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology - Service Provider Interface">AT-SPI</abbr>, fire children-changed:remove followed by children-changed:add for the new object</li>
		</ul>
Comment 2 Andi Snow-Weaver 2009-08-06 21:12:41 UTC
Looks like this might be applicable to section 4.3, second table (Changes to Document content or node visibility), specifically the scenario "When a subtree is moved"?
Comment 3 Andi Snow-Weaver 2009-09-04 14:36:04 UTC
The sections have now been renumbered. Changes to document content or node visibility is now section 3.8.1.
Comment 4 Andi Snow-Weaver 2009-09-04 15:10:44 UTC
done for everything except EVENT_OBJECT_REORDER. Add to MSAA column, then ping Cynthia.
Comment 5 Andi Snow-Weaver 2009-09-11 21:18:14 UTC
Cynthia, please review the second table in section 3.8.3 to see if the MSAA events are correct.
Comment 6 Andi Snow-Weaver 2009-09-28 20:33:18 UTC
I may have been too quick to assume that these bullets are not associated with dynamic role changes. See the second question in section 5.6 Roles (error handling) http://www.w3.org/WAI/PF/aria-implementation/#error-handling_roles
Comment 7 Andi Snow-Weaver 2010-01-05 15:35:30 UTC
Cynthia to send second table to the Windows team for verification.

Dynamic role changes is now addressed in 4.4 Role Mapping section.
Comment 8 Andi Snow-Weaver 2010-01-12 16:40:11 UTC
Waiting for Windows team review. 
Comment 9 Andi Snow-Weaver 2011-01-17 22:11:45 UTC
Ignore the title as it's confusing. Cynthia, please review the "Table of document change scenarios and events to be fired in each API" in section "5.8.2. Changes to document content or node visibility"

http://www.w3.org/WAI/PF/aria-implementation/#mapping_events_visibility
Comment 10 Andi Snow-Weaver 2011-01-21 17:17:52 UTC
Still need David's help on sorting out the special instructions for IA2 and ATK implementations wrt frame and iframe elements.
Comment 11 Andi Snow-Weaver 2011-01-28 21:10:46 UTC
Ignore previous comment. Entered in the wrong bug.
Comment 12 Andi Snow-Weaver 2011-01-28 21:11:46 UTC
re-copying action for Cynthia to clarify:

Ignore the title as it's confusing. Cynthia, please review the "Table of
document change scenarios and events to be fired in each API" in section
"5.8.2. Changes to document content or node visibility"

http://www.w3.org/WAI/PF/aria-implementation/#mapping_events_visibility