A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Behavior Attachment: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 37: | Line 37: | ||
| Inheritance | | Inheritance | ||
|- valign="top" style="border-bottom: 1px solid LightGray;" | |- valign="top" style="border-bottom: 1px solid LightGray;" | ||
! align="right" | Symptoms | |||
| | |||
* It is expected that an element may abruptly enter or exit association with the behavior. | |||
* There is a desire to not intrude on the original properties of an element. | |||
| | |||
* There is only one behavior that is typically associated with an element. | |||
* There is a desire to minimize the time when an element has no associated behavior. | |||
|- valign="top" style="border-bottom: 1px solid LightGray;" | |||
! align="right" | Examples of Use | ! align="right" | Examples of Use | ||
| | | |
Revision as of 21:27, 5 July 2011
WORK IN PROGRESS
- element is DOM element.
- content is DOM content.
- document is HTML document
Inheritance and Shadow DOM
What if an inherited element already has a shadow DOM subtree? In this case, the descendant has two options:
- Use
inherited
element. The inherited DOM subtree will be inserted in place of this element. Neither descendant nor ancestor will be able to access each other's subtrees. - Disregard the inherited shadow subtree. The inherited DOM subtree will still be created and continue to exist, but it will not be rendered (a "ghost tree"). This is necessary to ensure that the ancestor element's behavior is not affected with override.
Interaction of Element and Decorator Behavior Attachment
Since both behavior attachment models can exists in the same document, we must provide a way for the two to coexist on the same element.
- When a decorator is applied with an element with a shadow DOM subtree, the element subtree is treated as inherited.
- Order of
content
application: thecontent
elements contained in the inherited shadow DOM tree are applied last. This way, if both descendant or decorator claim a direct child, it will appear to the inherited tree as if there's nothing there.
Comparison Between Decorator and Element Behavior Attachment
Decorator | Element | |
---|---|---|
Purpose | Give existing content new behavior and/or appearance. | Create new content building blocks. |
Paradigm | Aspect-Oriented Programming | Object-Oriented Programming |
Compartmentalization and Reuse Vehicle | Aspect | Inheritance |
Symptoms |
|
|
Examples of Use |
|
|
Identity | Does not change the identity of the element. | Creates a new type of element. |
Lifetime | Transient, added and removed dynamically. | Permanent, originates with the element’s creation and exists through the lifetime. |
Environment | Foreign document or limited control of content. | Full control of content. |
Defining Traits |
|
|
Shadow Tree | Each decorator must have its own shadow subtree, and the aggregate shadow tree of an element is composed out of these subtrees. | Only one tree, initialized as the element is created. Inherited shadow trees can be reused, nested in the element's tree. |
DOM API | Should avoid adding any extra methods or properties to the DOM element that’s being decorated. | Explicitly interested in exposing methods or properties on the DOM element as its API. |
Analysis of Existing Specifications and Implementations
What does XBL2 do?
- There are two ways to bind: using binding element (inline or via external document) and using CSS. The former somewhat matches the notion to be element behavior, and the latter is the decorator behavior. However, there is no distinct difference in the attachment mechanism.
- Inheritance is entirely self-contained, using “extends” attribute. However, the prototype chain of the implementation object is fixed up to follow inherited bindings.
- There is a fair bit of machinery specified to marry the aspect and inheritance concepts seamlessly.
- There is no notion of extending DOM elements.
What does XBL1 do?
- There does not seem to be a separation between these two decorator and element behavior attachment. The http://mxr.mozilla.org/mozilla2.0/source/toolkit/content/xul.css seems to indicate the need for element attachment.
What does HTC do?
- HTC does not have the concept of shadow DOM, but the specified behavior is firmly an element behavior attachment.
What does sXBL do?
- It appears that the spec is abandoned, but the gist is similar to XBL2, except there is only one shadow tree, direct access to shadow subtree, and a binding model that seems to indicate element behavior attachment, but using decorator API.