DOM observer triggers will need to hook into the complete API surface for DOM read/write. A first approximation would be to identify read/write attributes and functions in the WebIDL specification of Node and its sub-interfaces. E.g.,
git clone https://github.com/mdittmer/web-apis.git
cd web-apis/data/idl/blink
node
const fs = require('fs')
const data = JSON.parse(fs.readFileSync('processed.json'))
const Node = data.filter(x => x.name === 'Node')[0]
const nodeChildren = data.filter(x => x.inheritsFrom === 'Node')
const nodeChildrenNames = nodeChildren.map(x => x.name)
/* ... */
Once the collection of relevant attributes and functions is identified, each one can have a Hook+PubHook that a DOMReadTrigger and DOMWriteTrigger can aggregate over.
DOM observer triggers will need to hook into the complete API surface for DOM read/write. A first approximation would be to identify read/write attributes and functions in the WebIDL specification of
Nodeand its sub-interfaces. E.g.,git clone https://github.com/mdittmer/web-apis.git cd web-apis/data/idl/blink nodeOnce the collection of relevant attributes and functions is identified, each one can have a Hook+PubHook that a
DOMReadTriggerandDOMWriteTriggercan aggregate over.