Component Model Discussion - Revision history

Morrita: /* Loading and Life Cycle */

2011-10-12T06:41:49Z

Loading and Life Cycle

← Older revision		Revision as of 06:41, 12 October 2011
Line 75:		Line 75:
	** <span style="color:blue">assumption: don't do anything</span>		** <span style="color:blue">assumption: don't do anything</span>
	* packaging		* packaging
	* is it possible to rename a component? e.g., to avoid name clashes?
	** <span style="color:blue">assumption: no</span>
	* define all edge cases and “unhappy” cases. Examples: constructor throws exception (general case), constructor throws exception during parsing		* define all edge cases and “unhappy” cases. Examples: constructor throws exception (general case), constructor throws exception during parsing

	=== <span style="color: #00AA88">Later</span> ===		=== <span style="color: #00AA88">Later</span> ===

			* is it possible to rename a component? e.g., to avoid name clashes?
			** <span style="color:blue">assumption: no</span>
	* is it possible to have a scoped (private) names, e.g., for private components?		* is it possible to have a scoped (private) names, e.g., for private components?
	** <span style="color:blue">assumption: no</span>		** <span style="color:blue">assumption: no</span>
	* Is it possible to undefine a component? (if yes, how?)		* Is it possible to undefine a component? (if yes, how?)
	** <span style="color:blue">assumption: no</span>		** <span style="color:blue">assumption: no</span>


	== Registration ==		== Registration ==

Annevk: /* Soon */ suggest binding=""

2011-10-12T05:36:01Z

Soon: suggest binding=""

← Older revision		Revision as of 05:36, 12 October 2011
Line 71:		Line 71:

	* loading mechanism (syntax)		* loading mechanism (syntax)
			:[[User:Annevk\|Annevk]]: Have a binding="" attribute on the root element (similar to manifest="")?
	* How to handle definition after use		* How to handle definition after use
	** <span style="color:blue">assumption: don't do anything</span>		** <span style="color:blue">assumption: don't do anything</span>

Rolandsteiner: /* Soon */ move iframe assumption to correct list item... :P

2011-10-12T04:51:17Z

Soon: move iframe assumption to correct list item... :P

← Older revision		Revision as of 04:51, 12 October 2011
Line 155:		Line 155:
	* To what degree is isolation/confinement really necessary? (scripts? DOM access? CSS properties?)		* To what degree is isolation/confinement really necessary? (scripts? DOM access? CSS properties?)
	* How far is isolation/confinement handling for components similar to <iframe sandbox>?		* How far is isolation/confinement handling for components similar to <iframe sandbox>?
			* Can we substitute isolation with <iframe>s?
	** <span style="color:blue">assumption: not in a very satisfactory manner</span>		** <span style="color:blue">assumption: not in a very satisfactory manner</span>
	* Can we substitute isolation with <iframe>s?
	* Are instances of the same component isolated from each other?		* Are instances of the same component isolated from each other?
	** <span style="color:blue">assumption: yes, but they should be able to set up shared data structures</span>		** <span style="color:blue">assumption: yes, but they should be able to set up shared data structures</span>

Rolandsteiner: /* Soon */ add assumption to iframe

2011-10-12T04:50:41Z

Soon: add assumption to iframe

← Older revision		Revision as of 04:50, 12 October 2011
Line 154:		Line 154:

	* To what degree is isolation/confinement really necessary? (scripts? DOM access? CSS properties?)		* To what degree is isolation/confinement really necessary? (scripts? DOM access? CSS properties?)
	* How far is isolation/confinement handling for components similar to <iframe>?		* How far is isolation/confinement handling for components similar to <iframe sandbox>?
			** <span style="color:blue">assumption: not in a very satisfactory manner</span>
	* Can we substitute isolation with <iframe>s?		* Can we substitute isolation with <iframe>s?
	* Are instances of the same component isolated from each other?		* Are instances of the same component isolated from each other?
Line 168:		Line 169:
	* Can isolated components position content outside the host boundary rect? (if not, problems with, e.g., +1 widget)		* Can isolated components position content outside the host boundary rect? (if not, problems with, e.g., +1 widget)
	** <span style="color:blue">assumption: yes</span>		** <span style="color:blue">assumption: yes</span>


	== Declarative syntax ==		== Declarative syntax ==

Rolandsteiner: /* Issues */ add spacing

2011-10-12T02:30:45Z

Issues: add spacing

← Older revision		Revision as of 02:30, 12 October 2011
Line 14:		Line 14:
	* '''<span style="color: #008866">Soon</span>''': to be included in V1 spec		* '''<span style="color: #008866">Soon</span>''': to be included in V1 spec
	* '''<span style="color: #00AA88">Later</span>''': issues to be discussed for later versions of the spec		* '''<span style="color: #00AA88">Later</span>''': issues to be discussed for later versions of the spec


	== CSS and Rendering ==		== CSS and Rendering ==
Line 25:		Line 26:
	* tab-index behavior		* tab-index behavior
	* z-order behavior		* z-order behavior


	== Shadow Nodes ==		== Shadow Nodes ==
Line 62:		Line 64:
	** on rebinding? (provided CSS 'binding' is possible)		** on rebinding? (provided CSS 'binding' is possible)
	* event on component registration?		* event on component registration?


	== Loading and Life Cycle ==		== Loading and Life Cycle ==
Line 142:		Line 145:

	* Attribute/property forwarding.		* Attribute/property forwarding.


	== Isolation and Confinement ==		== Isolation and Confinement ==

Rolandsteiner: /* Now */ removed layer question

2011-10-12T02:29:36Z

Now: removed layer question

← Older revision		Revision as of 02:29, 12 October 2011
Line 19:		Line 19:
	* [http://wiki.whatwg.org/index.php?title=Component_Model_Discussion:_Rendering rendering sub-page]: discussions on rendering details		* [http://wiki.whatwg.org/index.php?title=Component_Model_Discussion:_Rendering rendering sub-page]: discussions on rendering details
	* [http://wiki.whatwg.org/wiki/Component_Model_CSS_Brainstorming CSS brainstorming page]: brainstorming on alternative solutions to styling		* [http://wiki.whatwg.org/wiki/Component_Model_CSS_Brainstorming CSS brainstorming page]: brainstorming on alternative solutions to styling

	~~=== <span style="color: #006633">Now</span> ===~~

	* Do components create a layer?
	** <span style="color: blue">assumption: no</span>
	~~::[[User:Dglazkov\|Dglazkov]]: isn't this an implementation detail?~~

	=== <span style="color: #008866">Soon</span> ===		=== <span style="color: #008866">Soon</span> ===

Rolandsteiner: /* CSS and Rendering */ make tab-index and z-order "soon"

2011-10-11T22:49:25Z

CSS and Rendering: make tab-index and z-order "soon"

← Older revision		Revision as of 22:49, 11 October 2011
Line 29:		Line 29:

	* styling of rendering children of <content> (partially discussed in the [http://wiki.whatwg.org/wiki/Component_Model_CSS_Brainstorming CSS brainstorming page]).		* styling of rendering children of <content> (partially discussed in the [http://wiki.whatwg.org/wiki/Component_Model_CSS_Brainstorming CSS brainstorming page]).

	~~=== <span style="color: #00AA88">Later</span> ===~~

	* tab-index behavior		* tab-index behavior
	* z-order behavior		* z-order behavior


	== Shadow Nodes ==		== Shadow Nodes ==

Rolandsteiner: /* Issues */ change descriptions of now/soon/later

2011-10-11T22:48:48Z

Issues: change descriptions of now/soon/later

← Older revision		Revision as of 22:48, 11 October 2011
Line 11:		Line 11:
	= Issues =		= Issues =

	* '''<span style="color: #006633">Now</span>''': ~~issues regarding parts that are~~ already ~~implemented~~		* '''<span style="color: #006633">Now</span>''': in the spec draft and/or already in use for internal components
	* '''<span style="color: #008866">Soon</span>''': ~~issues regarding parts that we intend~~ to ~~implement soon~~		* '''<span style="color: #008866">Soon</span>''': to be included in V1 spec
	* '''<span style="color: #00AA88">Later</span>''': issues ~~regarding parts that we intend~~ to ~~postpone (may change substantially and/or not~~ be ~~implemented at all)~~		* '''<span style="color: #00AA88">Later</span>''': issues to be discussed for later versions of the spec

	== CSS and Rendering ==		== CSS and Rendering ==

Rolandsteiner: /* JavaScript */ re-add forwarding

2011-10-11T22:46:40Z

JavaScript: re-add forwarding

← Older revision		Revision as of 22:46, 11 October 2011
Line 149:		Line 149:
	** <span style="color:blue">assumption: don't care</span>		** <span style="color:blue">assumption: don't care</span>

			=== <span style="color: #00AA88">Later</span> ===

			* Attribute/property forwarding.

	== Isolation and Confinement ==		== Isolation and Confinement ==

Rolandsteiner: /* Derivation */

2011-10-11T05:47:42Z

Derivation

← Older revision		Revision as of 05:47, 11 October 2011
Line 123:		Line 123:
	== Derivation ==		== Derivation ==

	=== <span style="color: #~~006633~~">~~Now~~</span> ===		=== <span style="color: #00AA88">Later</span> ===

	* should we do XBL-like inheritance?		* should we do XBL-like inheritance?
	** <span style="color:blue">assumption: no</span>		** <span style="color:blue">assumption: no</span>

	~~=== <span style="color: #00AA88">Later</span> ===~~

	* “aspect-oriented" components (components defining the parts they use, derived components can override or re-use specific parts, part names automatically become pseudos)		* “aspect-oriented" components (components defining the parts they use, derived components can override or re-use specific parts, part names automatically become pseudos)
	* composition vs. inheritance (i.e., do we need inheritance at all, or can composition handle all use cases?)		* composition vs. inheritance (i.e., do we need inheritance at all, or can composition handle all use cases?)
	** <span style="color:blue">temporary assumption: composition only</span>		** <span style="color:blue">temporary assumption: composition only</span>


	== JavaScript ==		== JavaScript ==