openweb-weekly-22.html 15.3 KB

Raw Blame History Permalink

<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <style type="text/css" media="all">
    @import "/QA/2006/01/blogstyle.css";
    </style>
    <meta name="keywords" content='dom, html, html5, http, javascript, webapps' />
    <meta name="description" content="The Open Web Platform weekly summary is about HTML5 oldies, shadows and intents, and protocols." />
    <meta name="revision" content="$Id: openweb-weekly-22.html,v 1.11 2011/12/16 03:00:38 gerald Exp $" />
   <link rel="alternate" type="application/atom+xml" title="Atom" href="http://www.w3.org/QA/atom.xml" />
   <link rel="alternate" type="application/rss+xml" title="RSS 1.0" href="http://www.w3.org/QA/news.rss" />
   <title>Open Web Platform Weekly Summary - 2011-11-29 - 2011-12-04 - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2011/11/ben_schwarz_joining_csswg.html" title="Ben Schwarz joins CSSWG" />
   <link rel="next" href="http://www.w3.org/QA/2011/12/web_and_tv_ig_note_on_home_net.html" title="Web and TV IG note on Home Networking Scenarios published" />

   <!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
         xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description
    rdf:about="http://www.w3.org/QA/2011/12/openweb-weekly-22.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/450"
    dc:title="Open Web Platform Weekly Summary - 2011-11-29 - 2011-12-04"
    dc:identifier="http://www.w3.org/QA/2011/12/openweb-weekly-22.html"
    dc:subject="Open Web"
    dc:description="The Open Web Platform weekly summary is about HTML5 oldies, shadows and intents, and protocols."
    dc:creator="Karl Dubost"
    dc:date="2011-12-05T19:42:53+00:00" />
</rdf:RDF>
-->

    <!-- <script type="text/javascript" src="http://www.w3.org/QA/mt.js"></script>-->

</head>
<body class="layout-one-column">
      <div id="banner">
      <h1 id="title">
	<a href="http://www.w3.org/"><img height="48" alt="W3C" id="logo" src="http://www.w3.org/Icons/WWW/w3c_home_nb" /></a>
W3C Blog
</h1>
    </div>

    <ul class="navbar" id="menu">
        <li><strong><a href="/QA/" title="W3C Blog Home">[ W3C Blog ]</a></strong></li>
        <li><a href="/QA/Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
        <li><a href="/QA/Tools/" accesskey="3" title="Validators and other Tools">Tools</a></li>
        <li><a href="/2007/12/qa-blog-help/index#feedback">Feedback</a></li>
    </ul>
<div id="searchbox">
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<p id="formbox"><input type="text" size="15" class="textfield" name="q" accesskey="E" maxlength="255" /> <input type="submit" class="submitfield" value="Search" id="goButton" name="sa" accesskey="G" /> <input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /><input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org/QA" /><input type="hidden" name="domains" value="www.w3.org/QA" /></p>
</form>
</div>


    <div id="main"><!-- This DIV encapsulates everything in this page - necessary for the positioning -->

                     <p class="content-nav">
                        <a href="http://www.w3.org/QA/2011/11/ben_schwarz_joining_csswg.html">&laquo; Ben Schwarz joins CSSWG</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2011/12/web_and_tv_ig_note_on_home_net.html">Web and TV IG note on Home Networking Scenarios published &raquo;</a>
                     </p>

                        <h2 class="entry-header">Open Web Platform Weekly Summary - 2011-11-29 - 2011-12-04</h2>
                           <div class="entry-body">
                              <p>The <a href="http://www.w3.org/wiki/Open_Web_Platform">Open Web Platform</a> <a href="http://www.w3.org/QA/archive/open_web/">weekly</a> summary is about HTML5 oldies, shadows and intents, and protocols.</p>

<h3>HTML5</h3>

<p>Yehuda Katz and a few others have started a discussion on  <a href="http://lists.w3.org/Archives/Public/public-html/2011Nov/thread.html#msg234">Restoring PUT and DELETE</a> in HTML5 forms (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=1067">Issue 1067</a>). The Ruby on Rails Web framework is currently using a <a href="http://guides.rubyonrails.org/form_helpers.html#how-do-forms-with-put-or-delete-methods-work">hack for simulating PUT and DELETE</a>.</p>

<p>The Web is an amazing big pile of history. <code>border</code> attribute on <code>table</code> elements didn&rsquo;t have any units. Though people had a tendency to put units such as the wrong <code>&lt;table border="5px"&gt;</code>. So browsers repaired automagically to take into account only the beginning of the string and ignore any trailing characters. Sylvain Galineau (Microsoft) raised an <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15047">issue</a> because he thought it would create issues for microdata values. Ian Hickson mentioned that the incorrect values were not <strong>valid</strong> but fixed by the browser if wrong.</p>

<p><code>INS</code> and <code>DEL</code> elements which are used to track insertion and deletion of contents in HTML have a very simple model. So simple that according to Daniel Glazman (Disruptive Innovations), it is <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=13057">not easily implementable</a> in any useful way for authoring tools.</p>

<p>A Community Group has been proposed to <a href="http://www.w3.org/community/groups/proposed#html5spec">discuss ideas around the future of HTML and associated features</a>.</p>

<h3>Web Apps</h3>

<p>Webkit has a <a href="https://bugs.webkit.org/show_bug.cgi?id=73528">proposed patch</a> for the <a href="http://www.w3.org/TR/netinfo-api/">Network Information API</a>. This is an interesting API because it allows to create apps which behave differently depending if the network is 3g, wifi, etc. For example, imagine a <strong>responsive Web design</strong> where images of adequate sizes are sent depending on the type of network which gives a good idea of what could be the bandwidth.</p>

<p>Rich Tibbet (Opera) has proposed a <a href="http://richtr.tumblr.com/post/12929135260/a-better-model-for-web-intents">model for the Web intents</a> work.</p>

<p>Simon Pieters (Opera) wanted an <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=15007">API to queue a task</a>. After discussing about the opportunity of such a need, Glenn Maynard proposed a piece of code that finally Simon extended.</p>

<pre><code>var queueTask = function(task) {
    var mc = new MessageChannel();
    var args = [].slice.call(arguments, 1);
    mc.port1.onmessage = function(){
        this.onmessage = null; task.apply(task, args);
        };
    mc.port2.postMessage(null);
    };
queueTask(function(arg) { console.log(arg, this) }, "test");
</code></pre>

<p>Dimitri Glazkov (Chromium team) has proposed a high level <a href="http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html">overview of Web Components for Web Developers</a>.</p>

<h3>DOM</h3>

<p>The <code>setAttributeNS()</code> is <a href="http://www.w3.org/mid/op.v5pue1ha64w2qv@annevk-macbookpro.local">implemented differently</a> in IE, Firefox, Webkit and Opera. The discussion, which started on the mutability of attributes, led to discuss about simplifying the platform for HTML documents by removing the namespacing of attributes. According to Jonas Sicking (Mozilla), that would also improve browser performances. There would still be needed for <code>XMLDocument</code> interface.</p>

<h3>HTTP</h3>

<p>When exchanging data in between client and server, there are a few techniques. One of them is XMLHttpRequest which helps inject a data flow into the page without reloading the full context. People often uses it to transfer JSON packaged data. Anne van Kestern (Opera) has added <code>json</code> response type to <a href="http://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html#the-responsetype-attribute">XMLHttpRequest</a>.</p>

<p>When a client and server interact on the Web, the server answer to client requests with 3 number codes. These have very specific meanings. For example, <code>200</code> means that the server has successfully answered the client request.  It is happening quite often that Web developers (specifically those developing Web APIs) lack some <a href="http://en.wikipedia.org/wiki/List_of_HTTP_status_codes">HTTP status code</a> to have a richer interactions between the client and the server. Mark Nottingham has been working for a while on <a href="http://tools.ietf.org/html/nottingham-http-new-status">new HTTP status code</a>.</p>

<p>HTTP/1.1 allows many types of characters. This has a tendency to create security issues when, for example in <a href="http://tools.ietf.org/html/rfc3875">CGI/1.1</a>, translating these characters into UNIX environment variables.  Some of them are not valid and/or parseable characters. Yutaka Oiwa <a href="http://www.w3.org/mid/4EDC3AC0.70803@aist.go.jp">brought</a> the subject on HTTPbis mailing list.</p>

<h3>Elsewhere</h3>

<ul>
<li><a href="http://codemirror.net/">CodeMirror</a> is a JavaScript library that can be used to create a relatively pleasant editor interface for code-like content ― computer programs, HTML markup, and similar.</li>
<li><a href="http://24ways.org/2011/unicode-range">Creating Custom Font Stacks with Unicode-Range</a></li>
<li><a href="http://blogs.msdn.com/b/ie/archive/2011/11/29/html5-for-applications-the-fourth-ie10-platform-preview.aspx">IE10 Preview 4th</a> has support for CORS.</li>
<li>Firefox seems likely after Chrome to support <a href="https://wiki.mozilla.org/Platform/Features/SPDY">SPDY</a></li>
</ul>


<p>This week, the theme of <a href="http://annevankesteren.nl/">Anne Van Kesteren</a>&rsquo;s <a href="http://blog.whatwg.org/weekly-encoding-woes">report</a> about Encoding woes and WebVTT.</p>

<p>This column is written by <a href="http://www.la-grange.net/karl/">Karl Dubost</a>, <a href="http://my.opera.com/karlcow/blog/">working</a> in the <a href="http://dev.opera.com/">Developer Relations team</a> at <a href="http://www.opera.com/">Opera Software</a>.</p>

                           </div>
                           <div id="more" class="entry-more">

                           </div>
                       <p class="postinfo">Filed by <a href="http://my.opera.com/karlcow/blog/">Karl Dubost</a> on December  5, 2011  7:42 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/http/">HTTP</a>, <a href="http://www.w3.org/QA/archive/open_web/">Open Web</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/w3c_life/">W3C Life</a>, <a href="http://www.w3.org/QA/archive/technology/web_applications_1/">Web Applications</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2011/12/openweb-weekly-22.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2011/12/openweb-weekly-22.html#comments">Comments (1)</a>
                                 | <a href="http://www.w3.org/QA/2011/12/openweb-weekly-22.html#trackback">TrackBacks (0)</a>
</p>


<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-909468">
<p class="comment-meta" id="c909468">
<span class="comment-meta-author"><strong>Philippe Le Hegaret </strong></span>
<span class="comment-meta-date"><a href="#c909468">#</a> 2011-12-05</span>
</p>
<div class="comment-bulk">
<p>IE10 Preview 4th has also support for TTML and WebVTT.</p>

</div>
</div>


  <div class="comments-open" id="comments-open">
<h3 class="comments-open-header">Leave a comment</h3>

<div class="comments-open-moderated">
   <p>
   Note: this blog is intended to foster <strong>polite
   on-topic discussions</strong>. Comments failing these
   requirements and spam will not get published. Please,
   enter your real name and email address. Every
   individual comment is reviewed by the W3C staff.
   This may take some time, thank you for your patience.
   </p>
   <p>
   You can use the following HTML markup (a href, b, i,
   br/, p, strong, em, ul, ol, li, blockquote, pre)
   and/or <a href="http://daringfireball.net/projects/markdown/syntax">Markdown syntax</a>.</p>
</div>

<div id="comments-open-data">
<form method="post" action="http://www.w3.org/QA/sununga/beach.pl" id="comments-form">
<h4>Your comment</h4>
<div id="comments-open-text">
  <textarea id="comment-text" name="text" rows="20" cols="100"></textarea><br />
<label for="comment-text">Write your comment text here. Remember, keep the discussion on topic and courteous.</label>
</div>

<h4>About you</h4>
<div id="comment-form-name">
  <input type="hidden" name="static" value="1" />
<input type="hidden" name="entry_id" value="9281" />
<input type="hidden" name="__lang" value="en" />
<label for="comment-author">Your Name</label>
<input id="comment-author" name="author" size="30" value="" />
</div>
<div id="comment-form-email">
<label for="comment-email">Your Email Address</label>
<input id="comment-email" name="email" size="30" value="" />
</div>

<div id="comments-open-footer">
<input type="submit" accesskey="s" name="post" id="comment-submit" value="Submit" />

</div>
</form>
</div>
</div>


<p id="gentime">This page was last generated on $Date: 2011/12/16 03:00:38 $</p>

      </div><!-- End of "main" DIV. -->

<address>

This blog is written by W3C staff and working group participants,<br />
&nbsp;and maintained by <a href="/People/CMercier/">Coralie Mercier</a>.<br />
Authorized parties may <a href="/QA/new">log in</a> to create a new entry.<br/>
<span id="poweredby">Powered by Movable Type, magpierss and a lot of Web Technology</span>
    </address>


    <p class="copyright">
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 1994-2011
      <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>&reg;
      (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
      <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
      <a href="http://www.keio.ac.jp/">Keio</a>),
      All Rights Reserved.
      W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
      <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
      and <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a>
      rules apply. Your interactions with this site are in accordance
      with our <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Public">public</a> and
      <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Members">Member</a> privacy
      statements.
    </p>

  </body>
</html>