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 13509 - describe what happens in with accessibility APIs when existing document is destroyed
Summary: describe what happens in with accessibility APIs when existing document is de...
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P3 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords: a11y, a11ytf
Depends on:
Blocks:
 
Reported: 2011-08-02 01:23 UTC by Cynthia Shelly
Modified: 2016-04-07 14:42 UTC (History)
7 users (show)

See Also:

Attachments

Description Cynthia Shelly 2011-08-02 01:23:32 UTC 
3.5.1 document.open(replace) should describe what happens to the accessibility APIs when the existing document is destroyed.
Comment 1 Benjamin Hawkes-Lewis 2011-08-02 06:42:39 UTC 
(In reply to comment #0)
> 3.5.1 document.open(replace) should describe what happens to the accessibility
> APIs when the existing document is destroyed.

What sort of surprising thing should happen? Is this an interoperability problem currently?
Comment 2 Charles McCathieNevile 2016-04-07 14:42:55 UTC 
Steve?