element-settings.js
The declarative registry of native element Content controls. Getters and setters edit stored markup through an undoable editor change.
Responsibility#
The declarative registry of native element Content controls. Getters and setters edit stored markup through an undoable editor change.
File characteristics#
- Source:
assets/element-settings.js - Lines in this release: 729
- Type: browser JavaScript
Named browser helpers#
blockPart, boxMediaSet, colsCount, fresh, hotspotNumbers, networkSet, noticeLabelSet, noticeTone, noticeToneSet, quoteSet, safeUrl, shareToggle, tableChoice, tablePicture, tabsShow, videoSource.
These functions are internal to the module unless an explicit public contract says otherwise. The list includes nested helpers and is not a global browser API.
Literal event listeners#
keydown. Dynamic event names may be assembled elsewhere. Event listeners must follow the owner document when the live device canvas moves page nodes.
Markup attributes used here#
data-cb-address, data-cb-ask, data-cb-autoplay, data-cb-dismiss, data-cb-done, data-cb-due, data-cb-duration, data-cb-every, data-cb-levels, data-cb-lightbox, data-cb-network, data-cb-overlay, data-cb-scroll, data-cb-share, data-cb-single, data-cb-start, data-cb-stay, data-cb-title, data-cb-video, data-cb-words, data-cb-zoom, data-ce-closed, data-ce-opened. These names can represent authored state, generated output, or temporary editor markers. Use the feature’s save contract before persisting them.
Integration and verification#
Load this file through the plugin’s normal enqueue path so its dependencies and configuration are present. Check the relevant feature after a saved reload, in the live device canvas where applicable, and on the published page. Editor-only UI should not become authored page content. See architecture for the lifecycle and responsive design for document movement.