Component Model Progressive Enhancement - Revision history

Rolandsteiner at 00:37, 29 October 2011

2011-10-29T00:37:12Z

← Older revision		Revision as of 00:37, 29 October 2011
Line 20:		Line 20:
	# Set <code>became</code> property on the existing instance to point to the newly created element.		# Set <code>became</code> property on the existing instance to point to the newly created element.

	[[User:Rolandsteiner\|RolandSteiner]] Does this mean an author may need to duplicate CSS selectors, e.g., if we have <tt><div becomes="x-foo" class="c"></tt> and a selector <tt>div.c</tt>, don't we then also need an equivalent selector <tt>x-foo.c</tt>? OTOH, is it a problem?		[[User:Rolandsteiner\|RolandSteiner]] Does this mean an author may need to duplicate CSS selectors, e.g., if we have <tt><div becomes="x-foo" class="c"></tt> and a selector <tt>div.c</tt>, don't we then also need an equivalent selector <tt>x-foo.c</tt>? OTOH, is it a problem? Perhaps more so in JS with querySelectorAll than in CSS?

Rolandsteiner: add question

2011-10-29T00:36:25Z

add question

← Older revision		Revision as of 00:36, 29 October 2011
Line 19:		Line 19:
	# Fire "<code>become</code>" event on the existing instance.		# Fire "<code>become</code>" event on the existing instance.
	# Set <code>became</code> property on the existing instance to point to the newly created element.		# Set <code>became</code> property on the existing instance to point to the newly created element.

			[[User:Rolandsteiner\|RolandSteiner]] Does this mean an author may need to duplicate CSS selectors, e.g., if we have <tt><div becomes="x-foo" class="c"></tt> and a selector <tt>div.c</tt>, don't we then also need an equivalent selector <tt>x-foo.c</tt>? OTOH, is it a problem?

Dglazkov: Created page with 'A. While adding an element to a DOM tree: # Check for existence of the `becomes` attribute. If the attribute exists: ## Check the value of the `becomes` at...'

2011-08-31T17:48:21Z

Created page with 'A. While adding an element to a DOM tree: # Check for existence of the <code>becomes</code> attribute. If the attribute exists: ## Check the value of the <code>becomes</code> at...'

New page

A. While adding an element to a DOM tree:
# Check for existence of the <code>becomes</code> attribute. If the attribute exists:
## Check the value of the <code>becomes</code> attribute against the names of already defined elements.
### If such element exists, go to step X.
### Otherwise, store a reference to this instance in a "may-become" table.

B. When a new element is registered:
# Check to see if there are any instances waiting in the "may-become" table for this element's name
# If so, collect all these instances and, for each instance, go to step X.

C. When the "becomes" attribute is set:
# If the element is in tree, go to step A 1.1.

X. Becoming another element (in Element existing instance).
# Create the element by the name, specified in the <code>becomes</code> attribute of the existing instance
# If the existing instance is already in document tree:
## execute renameNode (or something better) to replace the old element with the newly created element.
## Otherwise, insert newly create element in DOM tree.
# Fire "<code>become</code>" event on the existing instance.
# Set <code>became</code> property on the existing instance to point to the newly created element.

Component Model Progressive Enhancement - Revision history

Rolandsteiner at 00:37, 29 October 2011

Rolandsteiner: add question

Dglazkov: Created page with 'A. While adding an element to a DOM tree: # Check for existence of the becomes attribute. If the attribute exists: ## Check the value of the becomes at...'

Dglazkov: Created page with 'A. While adding an element to a DOM tree: # Check for existence of the `becomes` attribute. If the attribute exists: ## Check the value of the `becomes` at...'