openweb-weekly-07.html 20 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='html, html5, open web, webapps' />
    <meta name="description" content="For this 7th edition, the HTML WG had discussions about accessibility related to images and tables with a few formal objections. The Last Call of HTML5 is approaching at a fast pace. There are active discussions about FileAPI and IndexedDB, which are fundamental bricks to enable Web applications in the browser. In the meantime, the HTTP Working Group has published a new series of drafts." />
    <meta name="revision" content="$Id: openweb-weekly-07.html,v 1.24 2011/12/16 03:00:14 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-04-11 - 2011-04-17 - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2011/04/coming_soon_w3c_community_grou.html" title="Coming Soon: W3C Community Groups and Business Groups" />
   <link rel="next" href="http://www.w3.org/QA/2011/04/openweb-weekly-08.html" title="Open Web Platform Weekly Summary - 2011-04-18 - 2011-04-24" />

   <!--
<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/04/openweb-weekly-07.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/388"
    dc:title="Open Web Platform Weekly Summary - 2011-04-11 - 2011-04-17"
    dc:identifier="http://www.w3.org/QA/2011/04/openweb-weekly-07.html"
    dc:subject="Open Web"
    dc:description="For this 7th edition, the HTML WG had discussions about accessibility related to images and tables with a few formal objections. The Last Call of HTML5 is approaching at a fast pace. There are active discussions about FileAPI and IndexedDB, which are fundamental bricks to enable Web applications in the browser. In the meantime, the HTTP Working Group has published a new series of drafts."
    dc:creator="Karl Dubost"
    dc:date="2011-04-17T20:17:02+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/04/coming_soon_w3c_community_grou.html">&laquo; Coming Soon: W3C Community Groups and Business Groups</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2011/04/openweb-weekly-08.html">Open Web Platform Weekly Summary - 2011-04-18 - 2011-04-24 &raquo;</a>
                     </p>

                        <h2 class="entry-header">Open Web Platform Weekly Summary - 2011-04-11 - 2011-04-17</h2>
                           <div class="entry-body">
                              <p>Our  <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>. Details  from <a href="http://w3.org/html5/">HTML5</a> and broader topics such as Web apps discussions and HTTP. It is the 7th edition and I still have to learn how to publish this a little bit more in advance.</p>

<h3>HTML Working Group Decisions</h3>

<h4><code>border</code> attribute on <code>table</code> element - ISSUE-155</h4>

<p>There was a time when the only solution to have or remove lines representing the table cells was to set a <code>border</code> attribute. Since then, we can easily set those with CSS properties. That said <a href="http://www.w3.org/html/wg/tracker/issues/155">should the attribute still be conforming</a>? It has been <a href="http://www.w3.org/mid/90384D79-17F7-46BB-9D5E-F026B35A98FA@apple.com">decided</a> to adopt the <a href="http://www.w3.org/html/wg/wiki/ISSUE-155-CP1">change proposal</a> to enable all users to distinguish the cells of a table. <code>cellpadding</code> and <code>cellspacing</code> have not been addressed and if people feel that it should be, they will should open a separate issue. Reopening this issue would require to identify a substantial number of Non-CSS UAs, syndication systems, or editors that do draw borders on HTML tables by default and pages which depends on this behavior.</p>

<p><a href="http://www.w3.org/mid/20110415210855541549.c789c8fc@xn--mlform-iua.no">leif halvard silli</a> considers that the subsequent edits where not conform to the decision, and found out later <a href="http://www.w3.org/mid/20110416052305664529.6a28cd35@xn--mlform-iua.no">additional</a> information, and after objecting, finally <a href="http://www.w3.org/mid/20110418151801678978.5c7e8416@xn--mlform-iua.no">withdrew it</a>.</p>

<h4>prose for <code>img</code> element - ISSUE-31</h4>

<p>There was an <a href="http://www.w3.org/html/wg/tracker/issues/31">issue</a> about the prose used for <code>img</code> element in the specification. It has been <a href="http://www.w3.org/mid/4DACA45F.40908@intertwingly.net">decided</a>. The final adopted text is </p>

<blockquote>
  <p>An img element represents an image.</p>

  <p>The image given by the src attribute is the embedded content; the
  value of the alt attribute provides equivalent content for those who
  cannot process images or who have image loading disabled.</p>
</blockquote>

<h4>accessibility for <code>img</code> element - ISSUE-31, ISSUE-80</h4>

<p>There has been a very complex debate around validity, <code>title</code>, <code>aria-labelledby</code> attributes usage. There is currently more than one way to give explicit information about images, etc. Then <a href="http://www.w3.org/html/wg/tracker/issues/80">questions</a> <a href="http://www.w3.org/html/wg/tracker/issues/31">arised</a> around the right combination of features such as "should it be permitted to omit <code>alt</code> when <code>role=presentation</code> is specified?" or "to omit alt when the generator mechanism is present?" The <a href="http://www.w3.org/mid/34C11ACB-74E6-4CA6-9842-345BE6F526DF@apple.com">decision</a> gives a long summary of the issues at stake. Read it. The summary is:</p>

<ul>
<li>The presence of aria-labelledby does not make missing alt conforming.</li>
<li>The presence of role=presentation does not make missing alt conforming.</li>
<li>The presence of <code>&lt;meta name="generator"&gt;</code> makes missing alt conforming.</li>
<li>Use of private communications does not, in itself, make missing alt conforming.</li>
<li>The presence of title makes missing alt conforming.</li>
<li>The presence of figcaption makes missing alt conforming.</li>
</ul>

<p>Steve Faulkner <a href="http://www.w3.org/mid/BANLkTik1W-fdoHWyF7hguFCgBYeAYvFHyg@mail.gmail.com">formally objected</a> on having conformance when <code>title</code> is specified and <code>alt</code> is missing  (<a href="http://dev.w3.org/html5/status/formal-objection-status.html#ISSUE-031">recorded</a>) and also on <a href="http://www.w3.org/mid/BANLkTi=w66h0gagJwZ=UBF8KEro1Wrc-RQ@mail.gmail.com">the fact</a> that the HTML5 Last Call would have different normative decisions than WCAG 2.0. There also discussion on the <a href="http://www.w3.org/mid/20110419041039397679.b950dd81@xn--mlform-iua.no">capabilities of CMS</a> or <a href="http://www.w3.org/mid/BANLkTim8DtoY0U8T_ojyyCgz8_c8awdBbQ@mail.gmail.com">browsers</a> with regards to the <code>alt</code> attribute.</p>

<h3>Conversations</h3>

<h4>Proposals</h4>

<ul>
<li>Cameron Heavon-Jones makes a proposal for extending the attribute values for forms on input to be able to set the HTTP client headers. Read <a href="http://www.w3.org/mid/3D5B75F7-1385-422D-BC2C-9B67301476BF@gmail.com">Authentication Forms</a>. A bug has been <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10671">opened</a>.</li>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-April/thread.html#31200"><code>summary</code> and <code>details</code> elements' specification</a> by Tomasz Jamroszczak</li>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-April/thread.html#31241">Proposing <code>&lt;canvas&gt;.toBlob(contentType)</code></a> by Kyle Huey</li>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-April/thread.html#31192">Canvas.getContext error handling</a> by Glenn Maynard</li>
</ul>

<h4>Announcements</h4>

<ul>
<li><a href="http://www.brucelawson.co.uk/">Bruce Lawson</a> (Opera) has created a <a href="http://www.brucelawson.co.uk/2011/html5-gurus-on-twitter/">list of people to follow</a> on twitter for their frequent mentions of topics surrounding HTML5.</li>
<li>HTTP Working Group <a href="http://www.w3.org/mid/4DAC6DEE.3040603@gmx.de">published new drafts</a> for HTTP bis</li>
<li>Request for Comments for the March 10 Last Call Working Draft of <a href="http://www.w3.org/TR/2011/WD-eventsource-20110310/">Server-sent Events</a> and <a href="http://www.w3.org/TR/2011/WD-workers-20110310/">Web Workers</a>. send them to the following list by <strong>21 April</strong> 2011.</li>
<li><a href="http://www.w3.org/News/Public/pnews-20110418">W3C Public Newsletter</a> with the last published specifications. </li>
</ul>

<h4>Hot Topics</h4>

<ul>
<li>The discussion about  <a href="http://lists.w3.org/Archives/Public/public-html/2011Apr/0118.html#msg118">access on media/plugin metadata</a> is very active</li>
<li><a href="http://burningbird.net/">Shelley Powers</a> has published  <a href="http://blog.whatwg.org/whatwg-weekly-whatwg-goes-native">WHATWG Weekly: WHATWG goes Native!</a>. </li>
<li>Steve Faulkner <a href="http://lists.w3.org/Archives/Public/public-html/2011Apr/0237.html#msg237">disagrees</a> with some edits made in the specification around ARIA mappings, then Ian Hickson (Google, HTML5 Editor) agreed that he <a href="http://www.w3.org/mid/Pine.LNX.4.64.1104120310080.25791@ps20323.dreamhostps.com">misunderstood</a> the issue.</li>
<li>Boris Zbarsky (Mozilla) noted <a href="http://www.w3.org/mid/4DA6FAB0.7000507@mit.edu">Browser inconsistencies</a> in implementing name getters on forms and  form element collections</li>
<li>Rich Schwerdtfeger (IBM) started a discussion about <a href="http://www.w3.org/mid/OFFA710DCA.B84036BA-ON86257872.00509D6B-86257872.00512E9F@us.ibm.com">Canvas API accessibility</a>.</li>
<li>Willy Tarreau explained about dirty and unreliable hacks to provide proxy authentication in enterprise in <a href="http://www.w3.org/mid/20110414190440.GA21585@1wt.eu">Talking HTTPS to proxies</a></li>
<li>The discussion on <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html">WebSQL</a> and friends continues.</li>
<li><a href="http://www.w3.org/mid/BANLkTim8PwaF0Rn4LyoNVFgTy9Ushece7g@mail.gmail.com">FileWriter and read-only files</a></li>
<li><a href="http://www.w3.org/mid/BANLkTi=VDEfkJrfbq-D0vaSxn19nA9VmyA@mail.gmail.com">BlobBuilder.getBlob should clear the BlobBuilder</a></li>
<li>Jonas Sicking (Mozilla) <a href="http://www.w3.org/mid/BANLkTintNz_UP3TQfcaHevNMx-HDo16cXg@mail.gmail.com">started</a> a long thread about File.slice bug in FileAPI specification.</li>
<li><a href="http://www.w3.org/mid/4D9F1127.3060201@lachy.id.au">Support for matchesSelector()</a></li>
<li><a href="http://www.w3.org/mid/4DA32D6D.7070800@mozilla.com">Result of calling MultipleReads on FileReader</a></li>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-April/thread.html#31250">Decimal comma in numeric input</a> by <a href="http://www.cs.tut.fi/~jkorpela/">Jukka K. Korpela</a></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 April 17, 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/04/openweb-weekly-07.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2011/04/openweb-weekly-07.html#comments">Comments (4)</a>
                                 | <a href="http://www.w3.org/QA/2011/04/openweb-weekly-07.html#trackback">TrackBacks (0)</a>
</p>


<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-223383">
<p class="comment-meta" id="c223383">
<span class="comment-meta-author"><strong>Rich </strong></span>
<span class="comment-meta-date"><a href="#c223383">#</a> 2011-04-19</span>
</p>
<div class="comment-bulk">
<p>Hiya,
"The presence of makes missing alt conforming." Is there an attribute name missing here?</p>

</div>
</div>


<div class="comment" id="comment-224283">
<p class="comment-meta" id="c224283">
<span class="comment-meta-author"><strong>Karl Dubost <a class="commenter-profile" href="http://my.opera.com/karlcow/blog/"><img alt="Author Profile Page" src="http://www.w3.org/QA/sununga/mt-static/images/comment/mt_logo.png" width="16" height="16" /></a></strong></span>
<span class="comment-meta-date"><a href="#c224283">#</a> 2011-04-26</span>
</p>
<div class="comment-bulk">
<p>@Rich: Yup, my bad. I have fixed markup typo. Thanks for noticing.</p>

</div>
</div>


<div class="comment" id="comment-224324">
<p class="comment-meta" id="c224324">
<span class="comment-meta-author"><strong>Leslie Balakrishnan </strong></span>
<span class="comment-meta-date"><a href="#c224324">#</a> 2011-04-27</span>
</p>
<div class="comment-bulk">
<p>I am trying to settle an academic point with an associate. I was hoping you could help.</p>
<p>Many of my professors site your W3C Browser Statistics page to track the changes in the browser market user trends. I now have someone that disputes their validity.</p>

<p>How definitive do you consider your rankings to be and how do you arrive at your conclusions?</p>

<p>Any light you can shed on this would be greatly appreciated.</p>

</div>
</div>


<div class="comment" id="comment-224354">
<p class="comment-meta" id="c224354">
<span class="comment-meta-author"><strong>Karl Dubost <a class="commenter-profile" href="http://my.opera.com/karlcow/blog/"><img alt="Author Profile Page" src="http://www.w3.org/QA/sununga/mt-static/images/comment/mt_logo.png" width="16" height="16" /></a></strong></span>
<span class="comment-meta-date"><a href="#c224354">#</a> 2011-04-27</span>
</p>
<div class="comment-bulk">
<p>@leslie: Which page are you referring to? To the best of my knowledge the W3C doesn't have any Browser statistics page.</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="9072" />
<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:14 $</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>