-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
The UI's effect blocks are build by a quite complex DOM. Can we clean this up?
- UI build trees from
div.ui_number,div.ui_stringordiv.ui_object. Those are filled with spansspan.keyfollowed byspan.value, which may be filled by plain data or anotherdiv.ui_object, if the datatype sports a subtree - Every effect contains an
ui_objectat the top level, featuring an emptykeyspan and avaluespan wrapping everything. Is this two-level top wrapping needed? - The intertweened
span.keyandspan.valueseem useful, as they provide easy style and easy access to key and values in the code. - It's hard, despite useful, to use a key in the CSS, as it is stored as HTML text in a
span.keyfollowed by the targetspan.valuefield. As CSS sports no parent-selectors nor text-dependend selectors, one can not selectspan.valueordiv.ui_...elements sporting a certain key. This seems not to be easily solvable.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels