-
Develop a mutation observers subsystem that can automatically handle DOM updates on a page to read streaming text as it is presented to the user.
-
## ✨ Feature
We're adding all the collection of government information to the experiences. This makes a lot of the info on the Government Employee section of the profile redundant. This ticket explai…
-
Originally reported on Google Code with ID 6178
```
Mutation breakpoints need synchronous notifications about DOM changes, and mutation
observers don't provide those... yet.
Blocked by https://bugzi…
-
I think this could replace the transaction manager, though it might lead to less control over the undo/redo stack.
-
balat updated
2 years ago
-
It occurs that when you listen to DOM updates, for the complete list of all events as described on [MDN](https://developer.mozilla.org/en/docs/Web/API/MutationObserver), you mutation callback gets cal…
-
Currently the [spec states](https://docs.oasis-open.org/sarif/sarif/v2.1.0/errata01/os/sarif-v2.1.0-errata01-os-complete.html#_Toc141790669):
> SARIF defines an object model, the top level of which…
-
Context: https://github.com/ampproject/amp-react-prototype/pull/29#discussion_r341651128
The goal is to find a clear way to separate DOM mutations from external script and components.
Usually w…
-
Considerations:
- Prevent conflicts with replaceWith() (possibly through adding an attribute to a containing element)
- Add option for continuous replacement, potentially with max amount of times (e.g…
-
Originally reported on Google Code with ID 5586
```
Similarly to issue Issue 5490: Use DOM Mutation Observers as replacement for Mutation
events
MutationRecognizer (FBTest) should use DOM Mutation O…