openweb-weekly-17.html
17.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
<?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='css, dom, html5, w3c, webapps, working group' />
<meta name="description" content="In my tracking of the Open Web Platform for writing the weekly summary, I decided to be a bit more careful on what is happening on the HTML WG bug tracker. A lot of the discussion is happening there too. The biggest issue being the number of useless comments or spam." />
<meta name="revision" content="$Id: openweb-weekly-17.html,v 1.18 2011/12/16 03:00:27 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-08-30 - 2011-09-11 - W3C Blog</title>
<link rel="start" href="http://www.w3.org/QA/" title="Home" />
<link rel="prev" href="http://www.w3.org/QA/2011/09/do_not_track_standards_for_the.html" title="&quot;Do Not Track&quot; standards for the Web: The work is starting. " />
<link rel="next" href="http://www.w3.org/QA/2011/09/proposing_two_new_sw_interest.html" title="Proposing two new SW Interest Group Task Forces" />
<!--
<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/09/openweb-weekly-17.html"
trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/423"
dc:title="Open Web Platform Weekly Summary - 2011-08-30 - 2011-09-11"
dc:identifier="http://www.w3.org/QA/2011/09/openweb-weekly-17.html"
dc:subject="Open Web"
dc:description="In my tracking of the Open Web Platform for writing the weekly summary, I decided to be a bit more careful on what is happening on the HTML WG bug tracker. A lot of the discussion is happening there too. The biggest issue being the number of useless comments or spam."
dc:creator="Karl Dubost"
dc:date="2011-09-12T20:22:22+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/09/do_not_track_standards_for_the.html">« "Do Not Track" standards for the Web: The work is starting. </a> |
<a href="http://www.w3.org/QA/">Main</a>
| <a href="http://www.w3.org/QA/2011/09/proposing_two_new_sw_interest.html">Proposing two new SW Interest Group Task Forces »</a>
</p>
<h2 class="entry-header">Open Web Platform Weekly Summary - 2011-08-30 - 2011-09-11</h2>
<div class="entry-body">
<p>In my tracking of the <a href="http://www.w3.org/wiki/Open_Web_Platform">Open Web Platform</a> for writing the <a href="http://www.w3.org/QA/archive/open_web/">weekly</a> summary, I decided to be a bit more careful on what is happening on the <a href="http://www.w3.org/Bugs/Public/describecomponents.cgi?product=HTML%20WG">HTML WG bug tracker</a>. A lot of the discussion is happening there too. The biggest issue being the number of useless comments or spam. </p>
<h3 id="internationalizationi18n">Internationalization (I18N)</h3>
<p>The I18N Core Working Group has raised an <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13398">issue</a> about the HTML5 <a href="http://www.w3.org/TR/html5/text-level-semantics.html#the-q-element">definition of quotes property</a>. The default property should be defined by the language of the text and not by the locale of the browsers.</p>
<h3 id="webarchitecture">Web Architecture</h3>
<p>Tim Berners-Lee explains the architectural decision on <a href="http://lists.w3.org/Archives/Public/www-tag/2011Sep/0006">why fragment identifiers are not sent to the server</a> when they are deferenced.</p>
<h3 id="accessibilitya11y">Accessibility (A11y)</h3>
<p>Laura Carlson <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13960">proposed</a> to change example on how the <code>article</code> element is used. In HTML5 examples, the article element contains <code>heading</code> and <code>nav</code> elements. She is proposing to reserve the article for pure content in a way which enable screen readers to jump directly to the content avoiding navigation elements. </p>
<h3 id="htmlmarkup">HTML Markup</h3>
<p>Shaun Moss wants to <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-September/thread.html#33083">propose a <code>comment</code> element for blog posts</a>. A long discussion started.</p>
<h3 id="layout">Layout</h3>
<p>Eric Muller (Adobe) <a href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0655">has sent</a> to the Unicode Consortium a <a href="http://lists.w3.org/Archives/Public/www-style/2011Aug/att-0655/11327-vertical.html">proposal</a> to develop a Unicode property and algorithm to support Japanese layout. Japanese can be <a href="http://www.w3.org/TR/jlreq/">written horizontally or vertically</a> and it is important to be able to determine the orientation of the characters in vertical lines.</p>
<p>HTML5 Forms have client side validation with error messages. The tooltip is browser dependant and varies widely in style. Peter Gasston is <a href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0670">proposing</a> to add new properties for <a href="http://www.broken-links.com/2011/03/28/html5-form-validation/">styling these form validation messages</a>. </p>
<p>Peter Lins (HP) announced the new <a href="http://test.csswg.org/shepherd/">CSS Test Suite Management System</a>.</p>
<h3 id="dom">DOM</h3>
<p>Aryeh Gregor (Google) <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13974">would like to extend</a> the selection property in the <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/dom-core.html">DOM</a> for allowing more than one creating the possibility of buffering, manipulating, deleting them. He also proposed to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13975">remove the multiple ranges selection</a>. This property allows to select a piece of text in a Web page and then holding the command key to select another part of the text without having to do two operations. Only Firefox currently implements this feature.</p>
<p>Ryosuke Niwa (Google) <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1121">needs</a> events that <a href="http://ehsanakhgari.org/blog/2011-08-31/future-editing-web">fire before/after user editing action</a> and execCommand take place. He proposed the name <code>beforeEditAction</code> and <code>afterEditAction</code>.</p>
<p>Dominic Cooney (Google, Chromium) wants a way to <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1139">register new elements not necessary described in the specification</a>. For example, it could work doing something ala </p>
<pre><code>HTMLElement.register('x-contacts', ContactPicker);
</code></pre>
<blockquote>
<p>The first argument is an element name. The second is a constructor
function, whose prototype property points to an object which
introduces the API for contacts (eg a refresh method) and is wired up
to HTMLElement.prototype.</p>
</blockquote>
<p>Anne van Kesteren (Opera) notes that its the <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1142">backdoor to introduce proprietary markup</a> on the Web. The fallback behavior in absence of scripting is another issue. The discussion is still going on.</p>
<p>Anne van Kesteren (Opera) has removed the entity references from DOM Core (DOM4) and <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13980">then it modifies</a> the HTML5 specification. Entity references were enabling the creation of markup constructs in the doctype. It introduces a lot of complexities in the management of DOM Nodes. </p>
<p>Kentaro Hara (Google) has requested <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13991"><code>HashChangeEvent</code> constructor</a> to make all events constructable as well a <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13993"><code>PageTransitionEvent</code> constructor</a>. It has been <a href="http://html5.org/tools/web-apps-tracker?from=6550&to=6551">integrated right away in HTML5</a> specification. </p>
<p>Boris Zbarsky (Mozilla) notes that Gecko, WebKit and Presto have three different <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=14037">implementations of <code>window.XMLDocument</code></a>. There are discussions going on how it should be properly specced still taking into account the differences of implementations across browsers and the interoperability issues on legacy code.</p>
<h3 id="graphicscanvaswebgl">Graphics (Canvas, WebGL, …)</h3>
<p>Charles Pritchard (Jumis) needs a <code>baseline</code> property on the <a href="http://www.w3.org/TR/2dcontext/#textmetrics"><code>TextMetrics</code></a> object from <a href="http://dev.w3.org/html5/2dcontext/Overview.html">Canvas 2d</a>. <q>The baseline corresponds to the vertical offset of the anchor point</q>.</p>
<pre><code>var t = ctx.measureText('text span');
t == { width: int, baseline: int };
</code></pre>
<p>David Geary proposes the <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-August/033052.html">creation of two new methods in canvas 2D: Path</a> <code>getPath()</code>, which would return a path object representing the context’s current path, and <code>setPath(Path)</code>, which would set the current path. That would make it easier to drag objects on a path.</p>
<h3 id="performances">Performances</h3>
<p>Three Last Call Working Draft documents, <a href="http://www.w3.org/TR/2011/WD-performance-timeline-20110901/">Performance Timeline</a>, <a href="http://www.w3.org/TR/2011/WD-user-timing-20110901/">User Timing</a>, <a href="http://www.w3.org/TR/2011/WD-resource-timing-20110811/">Resource Timing</a>, have been published. The deadline of comments on the first two documents is September 22 and Resource Timing is September 15.</p>
<h3 id="protocolhttpxhr2">Protocol (HTTP, XHR2, …)</h3>
<p>To avoid having to rebuild mime messages from scratch, Charles Pritchard (Jumis) would like to <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1127">extend <code>FormData</code> object</a>. He is taking example in the <a href="http://code.google.com/apis/picasaweb/docs/2.0/developers_guide_protocol.html#PostPhotos">Picasa developer guide on posting photos</a> and a code <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1143">example</a>:</p>
<pre><code>var callback = function(blob) { xhr.send(blob); };
formData.toBlob(callback, 'multipart/form-data');
</code></pre>
<p>Julian Reschke () has rewritten the HTTPbis Working Draft to add information about the <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/0443">history of HTTP Redirection (3xx)</a> </p>
<p>Joel Martin wanted to be able to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13984">detect if the connection allows for binary data transmission</a> in Websockets. Simon Pieters (Opera) proposed to use the already existing <code>binaryType</code>. </p>
<pre><code>var binarySupported = typeof WebSocket.prototype.binaryType != 'undefined';
</code></pre>
<p>It seems that <a href="https://bugs.webkit.org/show_bug.cgi?id=67335">chrome implementation is incomplete</a> creating interoperability issues. It might be fixed in future versions.</p>
<h3 id="misc">Misc</h3>
<p>This week, the theme of <a href="http://annevankesteren.nl/">Anne Van Kesteren</a>’s <a href="http://blog.whatwg.org/weekly-end-of-last-call">report</a> is Parsing APIs.</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 & 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 September 12, 2011 8:22 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/09/openweb-weekly-17.html">Permalink</a>
| <a href="http://www.w3.org/QA/2011/09/openweb-weekly-17.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2011/09/openweb-weekly-17.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="9199" />
<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:27 $</p>
</div><!-- End of "main" DIV. -->
<address>
This blog is written by W3C staff and working group participants,<br />
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> © 1994-2011
<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>®
(<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>