Bugzilla

And Orca needs to pay attention to the events it is not ignoring both for text-field changes and for live-region changes. So having Orca ignore the events in question is not the answer -- at least not until we create new AT-SPI2 and ATK API specific to live regions (which I think would actually be a good idea, but that takes time).

Here's my tentative proposal:
1. Obviously text changes in editable fields MUST emit text-change notifications.
2. Anything which is an ARIA live region MUST emit text-change and/or children-change notifications.
3. Anything which doesn't fall into either of the above categories but is doing constant DOM updates, SHOULD NOT emit either. That's the old Matrix situation.
4. Any container which is potentially) updating actual information (e.g. a news site adding and removing articles, updating timestamps, etc.) SHOULD result in one notification on the container rather than a bunch.

Some examination of sites may be called for to figure out what doesn't fall into either 1 or 2, but some ideas:
* If it's just image changes, I don't want to be notified.
* If it's a non-editable field and only a tiny bit of text is changed, I don't want to be notified.
* If a big chunk of text is added or removed, I *do* want to be notified.

FWIW, Orca cares about these events for the following reasons:
* Notify the user (due to text changes in editable fields, present a live region update)
* To update its various caches of objects

And Orca needs to pay attention to the events it is not ignoring both for text-field changes and for live-region changes. So having Orca ignore the events in question is not the answer -- at least not until we create new AT-SPI2 and ATK API specific to live regions (which I think would actually be a good idea, but that takes time).

Here's my tentative proposal:
1. Obviously text changes in editable fields MUST emit text-change notifications.
2. Anything which is an ARIA live region MUST emit text-change and/or children-change notifications.
3. Anything which doesn't fall into either of the above categories but is doing constant DOM updates, SHOULD NOT emit either. That's the old Matrix situation.
4. Any container which is (potentially) updating actual information (e.g. a news site adding and removing articles, updating timestamps, etc.) SHOULD result in one notification on the container rather than a bunch.

Some examination of sites may be called for to figure out what doesn't fall into either 1 or 2, but some ideas:
* If it's just image changes, I don't want to be notified.
* If it's a non-editable field and only a tiny bit of text is changed, I don't want to be notified.
* If a big chunk of text is added or removed, I *do* want to be notified.

FWIW, Orca cares about these events for the following reasons:
* Notify the user (due to text changes in editable fields, present a live region update)
* To update its various caches of objects

And Orca needs to pay attention to the events it is not ignoring both for text-field changes and for live-region changes. So having Orca ignore the events in question is not the answer -- at least not until we create new AT-SPI2 and ATK API specific to live regions (which I think would actually be a good idea, but that takes time).

Here's my tentative proposal:
1. Obviously text changes in editable fields MUST emit text-change notifications.
2. Anything which is an ARIA live region MUST emit text-change and/or children-change notifications.
3. Anything which doesn't fall into either of the above categories but is doing constant DOM updates, SHOULD NOT emit either. That's the old Matrix situation.
4. Any container which is (potentially) updating actual information (e.g. a news site adding and removing articles, updating timestamps, etc.) SHOULD result in one notification on the container rather than a bunch.

Some examination of sites may be called for to figure out what doesn't fall into either 1 or 2, but some ideas:
* If it's just image changes, I don't want to be notified.
* If it's a non-editable element and only a tiny bit of text is changed, I don't want to be notified.
* If a big chunk of text is added or removed, I *do* want to be notified.

FWIW, Orca cares about these events for the following reasons:
* Notify the user (due to text changes in editable fields, present a live region update)
* To update its various caches of objects