Closed
Bug 255086
Opened 20 years ago
Closed 17 years ago
HTML updates not being properly fired via accessibility API
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: korn, Assigned: ginnchen+exoracle)
References
()
Details
(Keywords: access, Whiteboard: AP2)
1. Launch GOK
2. Launch Mozilla with some page
3. Bring up the GOK UI-Grab keyboard
4. Select a hyperlink on that keyboard - Mozilla goes to that web page (good)
5. Note that the UI-Grab keyboard doesn't update (bad).
Compare to gnome-help, where a new web page appearance is tracked by GOK, which
then updates its UI-Grab keyboard.
Reporter | ||
Updated•20 years ago
|
Whiteboard: AP2
Updated•18 years ago
|
Hardware: Sun → All
Comment 1•18 years ago
|
||
Internally we fire EVENT_REORDER on the parent of the change, along with EVENT_SHOW or EVENT_HIDE on the child which is changing.
This needs to be translated to the proper children-changed events.
It's not an HTML specific issue -- technically it can (and probably does) happen anywhere in the UI.
This is an important area for Web 2.0 / AJAX accessibility.
Comment 2•17 years ago
|
||
We have follow up bugs but the main issues -- missing events, is now fixed.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 3•17 years ago
|
||
David, you'll need to use the document load and reload events for Firefox 3.
Comment 4•17 years ago
|
||
I think this was working when testing my patch on http://bugzilla.gnome.org/show_bug.cgi?id=356702 but having the load and reload events will be handy.
Comment 5•17 years ago
|
||
On second thought... I was doing a workaround with GOK. Ignore comment #4
You need to log in
before you can comment on or make changes to this bug.
Description
•