584165 - changes are not exposed to assistive technology when modifying nodeValue

Status: RESOLVED WORKSFORME

(Core :: Disability Access APIs, defect)

Description

[Karel Simek]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; cs; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; cs; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8

Having a paragraph set to ARIA-LIVE="polite" and modified via JavaScript I have observed the following:

When text node is changed using nodeValue property, assistive technology doesn't get notified. Using innerHTML or textNode creation to modify content seems to work. As nodeValue manipulation is often presented as a valid way of changing text, it should get reported.

Reproducible: Always

Steps to Reproduce:
1. start up NVDA or JAWS
2. open http://karelsimek.php5.cz/index7.html
2. use the buttons to toggle between three methods (button number 3 is the faulty one)

or
1. create a div and set it to ari-live="polite"
2. create a Interval and set it to call some method
3. use nodeValue to change div content inside this method
Actual Results:  
text changes but no notification about changes are presented

Expected Results:  
presenting the updates region content (works with button number 1 and 2)

Comment 1

[Marco Zehe (:MarcoZ)]

I cannot confirm this using Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b3pre) Gecko/20100803 Minefield/4.0b3pre (.NET CLR 3.5.30729) and NVDA 2010.1 release. I hear "bananas" increasing when presisng the first button, "appes" being added when pressing the second, and "olives" being added when pressing the third one. Also the regular updates are spoken, with the different fruits being spoken once more with each update.

So this seems to be working fine in the latest trunk and may be an isolated problem in Firefox 3.6.

Since we changed a lot of code, it is very likely that this got fixed along the way.

Comment 2

[Hubert Figuiere [:hub]]

given that this is apparently fixed in Firefox 4 and later (see comment #1) and that 3.6 will not get fixed, resolving.