openweb-weekly-16.html 16.2 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='api, dom, html5, tag, w3c, webapps' />
    <meta name="description" content=" I have decided to change a bit the style of weekly summary of the Open Web Platform. Instead of just going through the list of mails, I will try to focus on more specific things and give more context..." />
    <meta name="revision" content="$Id: openweb-weekly-16.html,v 1.24 2011/12/16 03:00:24 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 Monthly Summary - 2011-07-29 - 2011-08-29 - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2011/08/subject_from_innovation_to_sta.html" title="From Innovation to Standard" />
   <link rel="next" href="http://www.w3.org/QA/2011/09/do_not_track_standards_for_the.html" title="&amp;quot;Do Not Track&amp;quot; standards for the Web: The work is starting. " />

   <!--
<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/08/openweb-weekly-16.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/420"
    dc:title="Open Web Platform Monthly Summary - 2011-07-29 - 2011-08-29"
    dc:identifier="http://www.w3.org/QA/2011/08/openweb-weekly-16.html"
    dc:subject="Open Web"
    dc:description=" I have decided to change a bit the style of weekly summary of the Open Web Platform. Instead of just going through the list of mails, I will try to focus on more specific things and give more context..."
    dc:creator="Karl Dubost"
    dc:date="2011-08-30T20:17:10+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/08/subject_from_innovation_to_sta.html">&laquo; From Innovation to Standard</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2011/09/do_not_track_standards_for_the.html">"Do Not Track" standards for the Web: The work is starting.  &raquo;</a>
                     </p>

                        <h2 class="entry-header">Open Web Platform Monthly Summary - 2011-07-29 - 2011-08-29</h2>
                           <div class="entry-body">

<p>I have decided to change a bit the style of  <a href="http://www.w3.org/QA/archive/open_web/">weekly</a> summary of the <a href="http://www.w3.org/wiki/Open_Web_Platform">Open Web Platform</a>. Instead of just going through the list of mails, I will try to focus on more specific things and give more context about them. <a href="http://annevankesteren.nl/">Anne Van Kesteren</a> published his <a href="http://blog.whatwg.org/weekly-undomanager">report</a> on August 24.</p>


<ul>
<li><p>&#8220;How to organize a W3C Specification&#8221; is a <a href="http://www.w3.org/mid/4E43C13B.4010706@gmail.com">common question</a> at W3C. This time it started about the DOM specifications. The argument falls both on side of the consistency, work style, and technology design. There is no ultimate and definitive answer. In my opinion, you need to choose the format that will maximize participation for your context. The <a href="http://www.w3.org/TR/qaframe-spec/">specification organization</a> might be also influenced by the way you want to <a href="http://www.w3.org/TR/spec-variability/">design the technology</a>.</p><li>
<li><p>A new group for the <a href="http://www.w3.org/community/webed/">Web Education/Evangelization community</a> has been opened. Chris Mills is the co-chair of the group with Doug Scheppers. People on the <a href="http://lists.w3.org/Archives/Public/public-webed/">mailing-list</a> have started to introduce themselves. Join! It is free.</p><li>
<li><p>A while ago, I have talked about the Shadow DOM. The <a href="http://www.w3.org/mid/CADh5Ky04=OEjoQ48FR+Xtcq5_936NmT=acJs9QGVVN891bkS5g@mail.gmail.com">discussion evolved</a> led by Dimitri Glazkov (Google) and Dominic Cooney (Google) into the <a href="http://wiki.whatwg.org/wiki/Component_Model">Component Model</a>, a way to introduce support for creating custom DOM elements enabling layout managers or author UI elements included in the page, but not really part of the page. It inherits from the work done on XBL, XBL2 and MS HTML components, but will be more modular. See also <a href="http://www.w3.org/mid/CADh5Ky0Zd8MSOpf9CzvbBTWpArQEjNDDVwcN8_WL+ka5MvdjTw@mail.gmail.com">Component Model Update</a> mail and also <a href="http://www.w3.org/mid/CAHnmYQ_y4kPW64HPh4RFKmf7cCc-9+XvDprCqMDOeRofC6adaw@mail.gmail.com">this one</a>. </p><li>
<li><p>Your days of DukeNukem are not over. There is a proposal floating for a <a href="https://wiki.mozilla.org/JoystickAPI">Joystick API</a>. With the rise of HTML5 games popularity, there is a growing interest for this proposal.</p><li>
<li><p><a href="http://www.w3.org/wiki/DOM/domcore/nagivator.registerProtocolHandler">registerProtocolHandler</a> gives the possibility to Web sites to <a href="http://updates.html5rocks.com/2011/06/Registering-a-custom-protocol-handler">become handlers for specific protocols</a>. It is currently implemented in Chrome 13. There was a proposal on the list to <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-August/032738.html">extend the protocol</a>. </p><li>
<li><p>Would it be nice to be able to define how to proceed with undo/redo features but inside the browser? Ryosuke Niwa (Google) has <a href="https://rniwa.com/editing/undomanager.html">proposed a specification</a> along <a href="https://rniwa.com/editing/undomanager-usecases.html">use cases</a>. Ian Hickson decided to <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-August/032987.html">remove the old UndoManager</a> so that people could focus on Ryosuke Niwa&#8217;s proposal.</p><li>
<li><p><a href="http://www.w3.org/mid/BANLkTinV0oMZ1yE4ctVx5ZYsZgjZfZLEzgb8eFWETHBQ4VKmow@mail.gmail.com">MouseLock</a> is a proposed API to give the possibility to block the mouse in some circumstances. Vincent Scheib (Google) covered some of the issues <a href="http://www.w3.org/mid/CAK-EfXn_9xCBXJcW4TE_1r==wqR-T1jOkJgwkcuM+rcM5AnNFA@mail.gmail.com">identified</a> with the proposal.</p><li>
<li><p>Digital images contains a lot of hidden metadata such as date, focal length, etc. These are contained in the <a href="http://en.wikipedia.org/wiki/Exif">EXIF</a> part of the image. Some camera includes the orientation of the image when taken. Tab Atkins (Google) is proposing to <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-August/032988.html">add a <code>naturalOrientation</code> property to the <code>img</code> element</a> so it could be used in-browser photo-editing tools.</p><li>
<li><p><strong>Be careful</strong> with the <a href="http://www.w3.org/TR/css3-flexbox/">CSS Flexbox</a> (a feature giving you the possibility to reorder the boxes in CSS). This is one of the CSS module which has been quickly implemented by some browsers vendors. Too quickly? Web developers have started to use it and there is already some legacy code online. Why legacy? Flexbox is going through major revisions with backward incompatible changes. Tab Atkins (Google) is working right <a href="http://www.w3.org/mid/CAAWBYDB8_XvrYKOrGU+mXB2BW9EpivT86JAPUGmO4hhn6cXBcg@mail.gmail.com">now on the layout algorithm</a>.</p><li>
<li><p>The Web is evolving from a Web of documents to a Web of applications. This creates new constraints and usages to the system. HTML5 created <code>history.pushState()</code> and <code>history.replaceState()</code> for managing the history of a navigation and gives proper and usable URIs. Ashok Malhotra (Oracle) <a href="http://www.w3.org/mid/4E58F166.2050802@oracle.com">published</a> a new version of a <a href="http://www.w3.org/2001/tag/">W3C TAG</a> finding on <a href="http://www.w3.org/2001/tag/doc/IdentifyingApplicationState-20110830.html">Identifying Application State</a>. </p><li>
<li><p>There is a <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13942">request</a> on allowing @autofocus for any elements having @tabindex property in HTML. This would give the possibility to get a frame like behavior for some blocks in the document. When people create non scrollable section in a Web page, it creates a load of secondary issues.</p><li>
<li><p>Channy Yunn has proposed a <a href="http://www.w3.org/community/groups/proposed/">Web Crypto API Community Group</a>. It has not been accepted yet. If you are interested, join the effort. If you need more information about the topic, see <a href="http://html5.creation.net/webcrypto-api/">Web Crypto API</a> and <a href="https://wiki.mozilla.org/Privacy/Features/DOMCryptAPISpec/Latest">DOM Crypto API</a></p><li>
<li><p>Aryeh Gregor (Google) has proposed to extend the DOM for allowing authors to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13958">specify modifiers for accesskeys</a>. Right now, it is not possible to reassign the modifier which is dependent on the system (for example, the command on macosx and Ctrl on windows).</p><li>
<li><p>When dealing with a document, you might want to change the name of an element in the DOM by another name.  Aryeh Gregor (Google) has <a href="http://aryeh.name/spec/editing/editing.html#set-the-tag-name">defined in the editing specification</a> an algorithm for it. The discussion revived an existing feature called <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#Document3-renameNode">renameNode</a>. The current property is still <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13971">missing features</a>, but there is a will to include it in DOMCore.</p><li>
</ul>

<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 &amp; Tools</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 August 30, 2011  8:17 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</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><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2011/08/openweb-weekly-16.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2011/08/openweb-weekly-16.html#comments">Comments (0)</a>
                                 | <a href="http://www.w3.org/QA/2011/08/openweb-weekly-16.html#trackback">TrackBacks (0)</a>
</p>


  <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="9186" />
<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:24 $</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>