Component Model Strawman: Isolation - Revision history

Rolandsteiner: /* Overview */

2011-10-29T00:33:11Z

Overview

← Older revision		Revision as of 00:33, 29 October 2011
Line 1:		Line 1:
	= Overview =		= Overview =

	~~The isolated components definition is a <tt>provide</tt> attributed HTML file which is loaded in separate namespace.~~
	~~It is basically a document loaded by an iframe. But it has different way for communicating with the host document.~~

	== Terms ==		== Terms ==

Rolandsteiner: /* Overview */

2011-10-29T00:32:48Z

Overview

← Older revision		Revision as of 00:32, 29 October 2011
Line 3:		Line 3:
	The isolated components definition is a <tt>provide</tt> attributed HTML file which is loaded in separate namespace.		The isolated components definition is a <tt>provide</tt> attributed HTML file which is loaded in separate namespace.
	It is basically a document loaded by an iframe. But it has different way for communicating with the host document.		It is basically a document loaded by an iframe. But it has different way for communicating with the host document.

	~~See also the "Isolation" section on [[Component_Model_Strawman:_Declarative_Syntax]].~~

	== Terms ==		== Terms ==

Rolandsteiner at 22:54, 28 October 2011

2011-10-28T22:54:11Z

← Older revision		Revision as of 22:54, 28 October 2011
Line 29:		Line 29:

	Whether or not a component is isolated should ideally be transparent to both the component and the hosting DOM.		Whether or not a component is isolated should ideally be transparent to both the component and the hosting DOM.

	~~= Approaches =~~

	= Loading an External HTML Resource =		= Loading an External HTML Resource =

Rolandsteiner: add Overview and Considerations

2011-10-28T22:53:51Z

add Overview and Considerations

← Older revision		Revision as of 22:53, 28 October 2011
Line 1:		Line 1:
	= Overview =		= Overview =

			The isolated components definition is a <tt>provide</tt> attributed HTML file which is loaded in separate namespace.
			It is basically a document loaded by an iframe. But it has different way for communicating with the host document.

			See also the "Isolation" section on [[Component_Model_Strawman:_Declarative_Syntax]].

			== Terms ==

			* '''Confined''': disallow a component from accessing the containing page. Useful when a page does not trust the component or its source.
			* '''Encapsulated''': disallow the containing page from accessing the internals of the component. Useful when a component wants to prevent a page from meddling with it.
			* '''Isolated''': a component that is both confined and encapsulated.

			== Considerations ==

			=== Autonomy ===

			Components should be autonomous entities that can be loaded and applied as a single building block. Avoid requiring extensive manipulations on both side of the page <=> component divide.

			This will also help in implementing decorators.

			=== Interface ===

			The interface of a component should be minimal and well defined. Embedding pages should not be required (nor able to in the case of encapsulation) to access, or even know about, the internals of a component. Conversely, the function of a component should not depend on being able to access the DOM or any other information of the hosting page that is not provided through an interface.

			The component should be able to apply and filter data and styles passed in as it sees fit.

			=== Transparency ===

			Whether or not a component is isolated should ideally be transparent to both the component and the hosting DOM.

			= Approaches =

	= Loading an External HTML Resource =		= Loading an External HTML Resource =

Morrita at 19:33, 28 October 2011

2011-10-28T19:33:20Z

← Older revision		Revision as of 19:33, 28 October 2011
Line 86:		Line 86:

	= Confined Hosting =		= Confined Hosting =


	If an author hosts an external HTML without specifying <tt>confined</tt> attribute,		If an author hosts an external HTML without specifying <tt>confined</tt> attribute,
	the HTML is hosted as a confined resource.		the HTML is hosted as a confined resource.

	A confined resource has its document object. ~~ANy~~ scripts inside the confined resource		A confined resource has its document object. Any scripts inside the confined resource
	are run on its own global object.		are run on its own global object.

			Conceptually, a confined resource is similar to a document in a cross-domain frame.
			For example, the script on the confined resource can make a XMLHttpRequest to its own domain, instead of the host domain.

	<pre>		<pre>
Line 116:		Line 117:

	</pre>		</pre>

			== Registered Elements in a Confined Resource ==

			The host document recognize an element name which is registered in the hosting confined documents, not only

Morrita at 18:21, 28 October 2011

2011-10-28T18:21:52Z

@@ Line 80: / Line 80: @@
      var shouldNotNull = document.querySelector("element[name=x-comment]");
      </script>
    </head>
 </html>
 </pre>

Morrita at 17:48, 28 October 2011

2011-10-28T17:48:29Z

@@ Line 1: / Line 1: @@
 = Overview =
 = Loading an External HTML Resource =
-The element registration and template definition are also done in a separate HTML.
+Effective markup vocabulary for the external HTML is limited.
 Agents only recognize the first <tt>head element</tt> and its descendant.
@@ Line 13: / Line 13: @@
 <html>
    <head>
-     <element for="x-comment">..</element>
+     <element name="x-comment">..</element>
    </head>
 </html>
@@ Line 19: / Line 19: @@
 </pre>
-The host element can load the html with element definition using a <tt>link</tt> element with its <tt>rel</tt> attribute set to <tt>component</tt>.
+== The host document ==
 <pre>
@@ Line 40: / Line 48: @@
    <head>
      <link rel=”component” type=”text/html” href="comment.html" confined>
    </head>
 </html>
 </pre>

Morrita: /* Loading an External HTML Resource */

2011-10-28T17:31:54Z

Loading an External HTML Resource

← Older revision		Revision as of 17:31, 28 October 2011
Line 7:		Line 7:
	The element registration and template definition are also done in a separate HTML.		The element registration and template definition are also done in a separate HTML.
	Effective markup vocabulary for the defining HTML is limited.		Effective markup vocabulary for the defining HTML is limited.
	Agents only recognize the first head element and its descendant.		Agents only recognize the first <tt>head element</tt> and its descendant.

	<pre>		<pre>

Morrita: /* Loading a HTML Resource */

2011-10-28T17:31:22Z

Loading a HTML Resource

← Older revision		Revision as of 17:31, 28 October 2011
Line 2:		Line 2:
	= Overview =		= Overview =

	= Loading a HTML Resource =		= Loading an External HTML Resource =

Morrita: /* Loading a HTML Resource */

2011-10-27T22:49:34Z

Loading a HTML Resource

@@ Line 26: / Line 26: @@
    <head>
      <link rel=”component” type=”text/html” href="comment.html">
    </head>
 </html>
 </pre>