MSHTML: virtualBuffer for embedded applications does not listen for DOM mutations #4798

Closed
nvaccessAuto opened this Issue Jan 14, 2015 · 3 comments

1 participant

@nvaccessAuto

Reported by mdcurran on 2015-01-14 03:51
in MSHTML virtualBuffers, we currently listen for DOM mutations (insertion and removal of DOM nodes) by using MSHTML's iMarkupPointer interfaces. However, we only request this for body and frameset nodes. Therefore, if you were to force creation of a virtualBuffer within an ARIA application that was deeper than the body node, NVDA would not listen for DOM mutations for the inner virtualBuffer.
We need to track whether an MSHTML controlFieldNode in a virtualBuffer is / will be the root of the backend's buffer or not, if it is, then this should be good enough to request DOM mutation listening, even if this node is not the body or a frameset.

@nvaccessAuto

Attachment domMutationInAndOutOfEmbeddedApp.html added by mdcurran on 2015-01-14 03:53
Description:
Testcase allowing for DOM mutations both in the main document, and within an embedded ARIA application.

@nvaccessAuto

Comment 1 by Michael Curran <mick@... on 2015-01-14 04:05
In [108c7d5]:
```CommitTicketReference repository="" revision="108c7d5d9c6306ab2168149a13d98800ec11dce1"
Merge branch 't4798' into next. Incubates #4798

Changes:
Added labels: incubating
@nvaccessAuto

Comment 2 by Michael Curran <mick@... on 2015-01-29 00:10
In [ce01493]:
```CommitTicketReference repository="" revision="ce01493b2a031d904f837c114419ec424d114b1e"
Merge branch 't4798'. Fixes #4798

Changes:
Removed labels: incubating
State: closed
@nvaccessAuto nvaccessAuto added this to the 2015.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment