<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>HTML5 Specifications Community Group</title>
	<atom:link href="http://www.w3.org/community/html5spec/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.w3.org/community/html5spec</link>
	<description></description>
	<lastBuildDate>Tue, 02 Apr 2013 08:03:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>HTML5 tag proposal : sandbox</title>
		<link>http://www.w3.org/community/html5spec/2013/04/02/html5-tag-proposal-sandbox/</link>
		<comments>http://www.w3.org/community/html5spec/2013/04/02/html5-tag-proposal-sandbox/#comments</comments>
		<pubDate>Tue, 02 Apr 2013 08:03:58 +0000</pubDate>
		<dc:creator>Loveneet S</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Benefits]]></category>
		<category><![CDATA[HTML5]]></category>
		<category><![CDATA[html5 spec]]></category>
		<category><![CDATA[HTML5 tag]]></category>
		<category><![CDATA[html5 w3.org community]]></category>
		<category><![CDATA[proposal]]></category>
		<category><![CDATA[sandbox]]></category>
		<category><![CDATA[tag]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/html5spec/?p=44</guid>
		<description><![CDATA[HTML has evolved beyond the original 22 tags; and so has evolved the web and the supporting infrastructure around consuming HTML. Things are getting even more interesting with content being published (and micro-published) and then embedded (videos, widgets, scripts) as &#8230; <a href="http://www.w3.org/community/html5spec/2013/04/02/html5-tag-proposal-sandbox/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><img alt="HTML5" src="http://current360.com/play/wp-content/uploads/2013/01/HTMLmainelement.jpg" class="aligncenter" width="600" height="375" /></p>
<p><strong>HTML</strong> has evolved beyond the original 22 tags; and so has evolved the web and the supporting infrastructure around consuming HTML. Things are getting even more interesting with content being published (and micro-published) and then embedded (videos, widgets, scripts) as content within content. The content within the content (or <em>micro-content</em>) is (a) infrastructure driven, like embedding of scriptlets for web tracking (b) consumption driven, like widgets for news, weather, jobs (c) interaction driven, like videos, slideshows, micro-documents, spreadsheet snapshots and (d) submissions like search forms, data-capture fields, etc.</p>
<p>The micro-content in large part is distributed as a code fragment wrapped either in &lt;script&gt;&nbsp;&nbsp;or an &lt;object&gt;/&lt;embed&gt; tag. As the offering of these services grow, together&nbsp;things will become sophisticated and mature in coming years. How far this script should be trusted? At the onset, the following questions need answering:</p>
<ul>
<li>Can the embedded script read the DOM of the page it is hosted in?</li>
<li>Can the script make further calls to the remote server using the script transport?</li>
<li>Can the script manipulate the CSS of the page it is hosted in?</li>
<li>Can the script attach event handlers?</li>
<li>Can the script call window.close() or document.replace() ?</li>
<li>Can the script launch a pop-up window while being rendered?</li>
<li>Is the script allowed to render non-textual content like video, audio, etc.?</li>
</ul>
<p>In today’s HTML and the User-Agent world, all the questions may be answered as YES.</p>
<p>The proposal is for a <strong>new tag called &lt;sandbox&gt;</strong> . <strong>&lt;sandbox&gt; provides hints to the user-agent for a fine grained and portable permission control of embedded content</strong>. Don’t want the script to capture user events?&nbsp;Only wanna allow page manipulation while being rendered? Say so in the attribute for the element. The proposed tag takes the browser security to a new level. The hints in the sandbox tag would inform the user-agent what the embedded script can/can’t do.</p>
<p>The IDL may look like this:</p>
<p><code>interface HTMLSandboxElement : HTMLElement {</p>
<p>readonly attribute allowRemoting;</p>
<p>readonly attribute allowStyleChange;</p>
<p>readonly attribute allowDOMScripting;</p>
<p>readonly attribute allowEventHandler;</p>
<p>readonly attribute allowSubmit;</p>
<p>boolean checkPermission(in DOMString attributeName);</p>
<p>}</p>
<p></code></p>
<h5>A sample HTML fragment (Web-Analytics example)</h5>
<p><code></p>
<p>&lt;sandbox allowRemoting="0" allowStyleChange="0"</p>
<p>allowEventHandler="1" allowSubmit="0"&gt;</p>
<p>&lt;script src="http://www.example-analytics.com/tracker.js" mce_src="http://www.example-analytics.com/tracker.js" &gt;</p>
<p>&lt;/script&gt;</p>
<p>&lt;script type="text/javascript"&gt;</p>
<p>_uacct = "UA-XXXXX";</p>
<p>Tracker();</p>
<p>&lt;/script&gt;&nbsp;</p>
<p>&lt;/sandbox&gt;</p>
<p></code></p>
<p>Another example&nbsp;HTML fragment (news widget in sidebar). By default allows content which is plain HTML with links, text and associated styles.</p>
<p><code></p>
<p>&lt;sandbox&gt;</p>
<p>&lt;script src="http://example.com/dailyheadlines.js" mce_src="http://example.com/dailyheadlines.js"</p>
<p>&lt;/script&gt;</p>
<p>&lt;/sandbox&gt;</p>
<p></code></p>
<p>Benefits:</p>
<ul>
<li>Fine-grained control while composing content (or application output) from multiple sources</li>
<li>Shared responsibility between page author and user-agent</li>
<li>Takes the browser security to a new level</li>
<li>Portable permissions instead of relying on individual user-agent configuration options for various permutations and combinations.</li>
</ul>
<p>Under what circumstances the new tag may not make sense:</p>
<ul>
<li>User-agents take full resposibility of such fine grained permissions through their own implementations and user configuration options</li>
<li>Micro-content, content inclusion etc. become passé</li>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/html5spec/2013/04/02/html5-tag-proposal-sandbox/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>A Propusal for A New  Pseudo Element Called :icon</title>
		<link>http://www.w3.org/community/html5spec/2012/09/18/a-propusal-for-a-new-pseudo-element-icon/</link>
		<comments>http://www.w3.org/community/html5spec/2012/09/18/a-propusal-for-a-new-pseudo-element-icon/#comments</comments>
		<pubDate>Tue, 18 Sep 2012 08:17:55 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/html5spec/?p=40</guid>
		<description><![CDATA[Take a look to this HTML5 code as shown here: &#60;menu type="toolbar"&#62; &#60;command type="radio" radiogroup="alignment" checked="checked" label="Left" icon="icons/alL.png" onclick="setAlign('left')"&#62; &#60;command type="radio" radiogroup="alignment" label="Center" icon="icons/alC.png" onclick="setAlign('center')"&#62; &#60;command type="radio" radiogroup="alignment" label="Right" icon="icons/alR.png" onclick="setAlign('right')"&#62; &#60;hr&#62; &#60;command type="command" disabled label="Publish" icon="icons/pub.png" onclick="publish()"&#62; &#60;/menu&#62; The &#8230; <a href="http://www.w3.org/community/html5spec/2012/09/18/a-propusal-for-a-new-pseudo-element-icon/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Take a look to this HTML5 code as shown <a title="here" href="http://www.w3.org/TR/html5/the-command-element.html" rel="external nofollow">here</a>:</p>
<pre>&lt;menu type="toolbar"&gt;
	&lt;command type="radio" radiogroup="alignment" checked="checked"
		label="Left" icon="icons/alL.png" onclick="setAlign('left')"&gt;
	&lt;command type="radio" radiogroup="alignment"
		label="Center" icon="icons/alC.png" onclick="setAlign('center')"&gt;
	&lt;command type="radio" radiogroup="alignment"
		label="Right" icon="icons/alR.png" onclick="setAlign('right')"&gt;
&lt;hr&gt;
	&lt;command type="command" disabled label="Publish" icon="icons/pub.png" onclick="publish()"&gt;
&lt;/menu&gt;</pre>
<p>The question is: Isn’t <code>icon=""</code> attribute here a presentation attribute?<br />
You might say yes, and it should be set using CSS like this:</p>
<pre>command.align-right{icon: '....'}</pre>
<p>However, this presentation attribute in turn needs presentation attributes! (position, padding&#8230;).</p>
<p>So, we need something in between: A Pseudo Element.<br />
A Pseudo Element is simply an attribute has attributes.</p>
<pre>&lt;command class="page-about"...&gt;&lt;/command&gt;
&lt;command class="domain-settings"...&gt;&lt;/command&gt;

.page-about:icon {
	content: char(ℹ);
	font: 10pt RichStyle;
	icon-position: top;
}

.domain-settings:icon {
	content: char(⚙);
	font: 10pt RichStyle;
	icon-position: top;
}</pre>
<p>Thus, <code>icon=""</code> as an HTML attribute for <code>&lt;command&gt;</code> should be deprecated.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/html5spec/2012/09/18/a-propusal-for-a-new-pseudo-element-icon/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Shameless Plug Tag</title>
		<link>http://www.w3.org/community/html5spec/2012/05/07/the-shameless-plug-tag/</link>
		<comments>http://www.w3.org/community/html5spec/2012/05/07/the-shameless-plug-tag/#comments</comments>
		<pubDate>Mon, 07 May 2012 03:02:55 +0000</pubDate>
		<dc:creator>Steven Gordon</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/html5spec/?p=33</guid>
		<description><![CDATA[Particularly with the rise in self promotional activities around Social Networks there is a need for a self promotional meta tag &#8211; distinct from factual content descriptive meta tags. &#60;meta name=&#8221;shameless&#8221; content=&#8221;Insert Shameless Plug Here&#8221;&#60;/&#62; &#60;shameless&#62;Insert Shameless Plug Here&#60;/shameless&#62;]]></description>
			<content:encoded><![CDATA[<p>Particularly with the rise in self promotional activities around Social Networks there is a need for a self promotional meta tag &#8211; distinct from factual content descriptive meta tags.</p>
<p>&lt;meta name=&#8221;shameless&#8221; content=&#8221;Insert Shameless Plug Here&#8221;&lt;/&gt;</p>
<p>&lt;shameless&gt;Insert Shameless Plug Here&lt;/shameless&gt;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/html5spec/2012/05/07/the-shameless-plug-tag/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>When A Form Should Start Validation?</title>
		<link>http://www.w3.org/community/html5spec/2012/05/05/when-a-form-should-start-validation/</link>
		<comments>http://www.w3.org/community/html5spec/2012/05/05/when-a-form-should-start-validation/#comments</comments>
		<pubDate>Sat, 05 May 2012 09:52:50 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Forms]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/html5spec/?p=25</guid>
		<description><![CDATA[Let&#8217;s take a look to this simple demo form: http://www.richstyle.org/demo-form.html I use the following code to style the validation issue: input:required + output::after, textarea:required + output::after { content: '*'; } input:invalid + output::after, textarea:invalid + output::after { content: '⨉';color: maroon &#8230; <a href="http://www.w3.org/community/html5spec/2012/05/05/when-a-form-should-start-validation/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Let&#8217;s take a look to this simple demo form:<br />
<a href="http://www.richstyle.org/demo-form.html" rel="external nofollow">http://www.richstyle.org/demo-form.html</a></p>
<p>I use the following code to style the validation issue:</p>
<pre>
input:required + output::after,
textarea:required + output::after { content: '*'; }

input:invalid + output::after,
textarea:invalid + output::after { content: '⨉';color: maroon }

input:valid + output::after,
textarea:valid + output::after { content: '✓';color: green }
</pre>
<p>The only thing looks unacceptable, is that the form validation process starts just when the form is loaded, whilst, it&#8217;s much better to start it in each input field independently,  as user starts write something in it.</p>
<p>So, I thought of inventing a new attribute called &#8220;start-validation&#8221; with the following values:</p>
<pre>
form {
	start-validation: on-load | on-focus | on-type | on-blur | on-submit;
}
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/html5spec/2012/05/05/when-a-form-should-start-validation/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Let&#8217;s free A and HREF!</title>
		<link>http://www.w3.org/community/html5spec/2012/04/24/lets-free-a-and-href/</link>
		<comments>http://www.w3.org/community/html5spec/2012/04/24/lets-free-a-and-href/#comments</comments>
		<pubDate>Tue, 24 Apr 2012 21:16:16 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[links]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/html5spec/?p=16</guid>
		<description><![CDATA[Take a look to this example: &#60;nav class="toolbar"&#62; &#60;ul&#62; &#60;li&#62;&#60;a herf="index.html"&#62;Home&#60;/a&#62;&#60;/li&#62; &#60;li&#62;&#60;a href="about.html"&#62;About&#60;/a&#62;&#60;/li&#62; &#60;li&#62;&#60;a href="downloads.html"&#62;Downloads&#60;/a&#62;&#60;/li&#62; &#60;li&#62;&#60;a href="contact.html"&#62;Contact&#60;/a&#62;&#60;/li&#62; &#60;li&#62;&#60;a href="javascript:bookmark()"&#62;Bookmark&#60;/a&#62;&#60;/li&#62; &#60;/ul&#62; &#60;/nav&#62; Isn&#8217;t better if it was possible to be written like this: &#60;toolbar&#62; &#60;li herf="index.html"&#62;Home&#60;/li&#62; &#60;li href="about.html"&#62;About&#60;/li&#62; &#60;li href="downloads.html"&#62;Downloads&#60;/li&#62; &#60;li &#8230; <a href="http://www.w3.org/community/html5spec/2012/04/24/lets-free-a-and-href/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Take a look to this example:</p>
<pre>&lt;nav class="toolbar"&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;a herf="index.html"&gt;Home&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href="about.html"&gt;About&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href="downloads.html"&gt;Downloads&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href="contact.html"&gt;Contact&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href="javascript:bookmark()"&gt;Bookmark&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/nav&gt;
</pre>
<p>
Isn&#8217;t better if it was possible to be written like this:
</p>
<pre>&lt;toolbar&gt;
	&lt;li herf="index.html"&gt;Home&lt;/li&gt;
	&lt;li href="about.html"&gt;About&lt;/li&gt;
	&lt;li href="downloads.html"&gt;Downloads&lt;/li&gt;
	&lt;li href="contact.html"&gt;Contact&lt;/li&gt;
	&lt;li href="javascript:bookmark()"&gt;Bookmark&lt;/li&gt;
&lt;/toolbar&gt;
</pre>
<p>
or even:
</p>
<pre>&lt;toolbar&gt;
	&lt;command herf="index.html"&gt;Home&lt;/command&gt;
	&lt;command href="about.html"&gt;About&lt;/command&gt;
	&lt;command href="downloads.html"&gt;Downloads&lt;/command&gt;
	&lt;command href="contact.html"&gt;Contact&lt;/command&gt;
	&lt;command href="javascript:bookmark()"&gt;Bookmark&lt;/command&gt;
&lt;/toolbar&gt;
</pre>
<p>
I mean why should I have to add <code>&lt;a&gt;</code> tag to every object/tag I want to link to something? Isn&#8217;t better if I were able to add <code>href=""</code> attribute to this object/tag without using <code>&lt;a&gt;</code> tag?
</p>
<p>
Why don&#8217;t we use <code>href=""</code> as a <em>global attribute</em>?
</p>
<p>
Likewise, think of using <code>&lt;a&gt;</code> tag without <code>href=""</code> when the link name = the link address:
</p>
<pre>&lt;p&gt;
.., you can download it from &lt;a&gt;http://example.com/downloads/&lt;/a&gt;.
&lt;/p&gt;
</pre>
<p>
instead of:
</p>
<pre>&lt;p&gt;
.., you can download it from &lt;a href="http://example.com/downloads/"&gt;http://example.com/downloads/&lt;/a&gt;.
&lt;/p&gt;</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/html5spec/2012/04/24/lets-free-a-and-href/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>A Unified Naming Attribute for Everything</title>
		<link>http://www.w3.org/community/html5spec/2012/02/20/a-unified-naming-attribute-for-everything/</link>
		<comments>http://www.w3.org/community/html5spec/2012/02/20/a-unified-naming-attribute-for-everything/#comments</comments>
		<pubDate>Mon, 20 Feb 2012 08:25:30 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/html5spec/?p=8</guid>
		<description><![CDATA[Hi all, I&#8217;m glad to participate with the first post in this group Has anyone thought of using label="" as a unified naming attribute; as an alternative to all naming tags and attributes: &#60;caption&#62; , &#60;label&#62;, &#60;legend&#62;, alt="", for="", title="", &#8230; <a href="http://www.w3.org/community/html5spec/2012/02/20/a-unified-naming-attribute-for-everything/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Hi all,</p>
<p>I&#8217;m glad to participate with the first post in this group <img src='http://www.w3.org/community/html5spec/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Has anyone thought of using <code>label=""</code> as a unified naming attribute; as an alternative to all naming tags and attributes:</p>
<p><code>&lt;caption&gt;</code> , <code>&lt;label&gt;</code>, <code>&lt;legend&gt;</code>, <code>alt=""</code>, <code>for=""</code>, <code>title=""</code>, <code>summary=""</code>.</p>
<p><code>title=""</code> attribute could be deprecated in favor of a CSS attribute called <code>title:</code> with the following values:</p>
<pre>{ title: attr(label) | attr(accesskey) | attr(label) attr(accesskey) | none }</pre>
<p>The typical way for <code>label=""</code> presentation is to use <code>:before</code> and <code>:after</code> pseudo elements; beside the <code>title:</code> CSS attribute.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/html5spec/2012/02/20/a-unified-naming-attribute-for-everything/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hello world!</title>
		<link>http://www.w3.org/community/html5spec/2012/02/14/hello-world/</link>
		<comments>http://www.w3.org/community/html5spec/2012/02/14/hello-world/#comments</comments>
		<pubDate>Tue, 14 Feb 2012 03:43:35 +0000</pubDate>
		<dc:creator>Ian Jacobs</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/html5spec/?p=1</guid>
		<description><![CDATA[Welcome to Community and Business Groups. This is your first post. Edit or delete it, then start blogging!]]></description>
			<content:encoded><![CDATA[<p>Welcome to <a href="http://www.w3.org/community/" rel="external nofollow">Community and Business Groups</a>. This is your first post. Edit or delete it, then start blogging!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/html5spec/2012/02/14/hello-world/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
