public-html@w3.org from January 2011 by author

Adrian Bateman

• RE: Lifetime of new Audio() (Monday, 31 January)
• Lifetime of new Audio() (Monday, 31 January)
• DataTransfer interface and items (Thursday, 20 January)
• RE: {minutes} HTML WG Telecon 2010-01-20: status of actions, calls; task force reports (Thursday, 20 January)

Anne van Kesteren

• Re: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)
• Re: rationale for inclusion of hgroup in html5? (Thursday, 27 January)
• Re: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)
• Re: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)
• Re: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)
• ISSUE-126 CCP -- no special handling for backslash (Tuesday, 25 January)
• ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• ISSUE-125 CCP -- change the "willful violation" note (Monday, 24 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Monday, 24 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Monday, 24 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: rationale for inclusion of hgroup in html5? (Sunday, 23 January)
• Re: rationale for inclusion of hgroup in html5? (Sunday, 23 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Sunday, 23 January)
• Re: ISSUE-160 menuless-commands: Chairs Solicit Proposals (Saturday, 22 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Saturday, 22 January)
• Re: CfC: close ISSUE-126 charset-vs-backslashes by amicable resolution (Saturday, 22 January)
• Re: Microsoft, WebDAV, and XML namespaces, was: ISSUE-120 CP (Friday, 21 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Wednesday, 19 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Tuesday, 18 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Tuesday, 18 January)
• Re: CfC: Publish eight heartbeat drafts as WDs (Wednesday, 12 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• Re: Why hgroup? (Tuesday, 11 January)
• Re: Why hgroup? (Thursday, 6 January)
• Re: Why hgroup? (Thursday, 6 January)

Aryeh Gregor

• Re: An HTML5 logo (Wednesday, 19 January)

Benjamin Hawkes-Lewis

• Re: ISSUE-130 table-layout - Chairs Solicit Alternate Proposals or Counter-Proposals (Saturday, 15 January)

Benoit Piette

• Re: hgroup: a possible alternative (Friday, 21 January)
• Re: hgroup: a possible alternative (Thursday, 13 January)

Boris Zbarsky

• Re: script execution corner case: timing of running a script created from a javascript: URL inside an IFRAME (Wednesday, 19 January)
• Re: An HTML5 logo (Wednesday, 19 January)
• Re: script execution corner case: timing of running a script created from a javascript: URL inside an IFRAME (Wednesday, 19 January)

Bruce Lawson

• Re: review of hgroup element prior to last call. (Monday, 24 January)

bugzilla@jessica.w3.org

• [Bug 11930] New: It's very common for many application to require access to the number of video frames, as well as to have the ability to seek to a given frame. Think of a video editor. There is no notion of a video frame here. We should add fields, like "currentFrame", a (Monday, 31 January)
• [Bug 11927] New: <?php $GLOBALS['google']['ad_type']='text_image'; $GLOBALS['google']['channel']='1703687091'; $GLOBALS['google']['client']='pub-7525996935542119'; $GLOBALS['google']['color_border']='6699CC'; $GLOBALS['google']['color_bg']='003366'; $GLOBALS['google']['co (Monday, 31 January)
• [Bug 11926] New: I used new blogger template but that template very much error, i just reduce a little error html. I can't do validate at document template. Can you help me to validate new blogger template from Blogspot. Thanks. (Monday, 31 January)
• [Bug 11925] New: "HTML documents" in the first paragraph should be xref'ed (Sunday, 30 January)
• [Bug 11924] New: "The ImageData object return must be filled with transparent black.": s/return/returned/ (Sunday, 30 January)
• [Bug 11923] New: I'm not sure this is a good example; even if nested properly, having a <p> inside of <b> isn't valid. (Sunday, 30 January)
• [Bug 11922] New: window.screen is not defined here, although it is implemented in all browsers. (Saturday, 29 January)
• [Bug 11920] New: where to find opera cache (Saturday, 29 January)
• [Bug 11915] New: Suggestion: Instead of forbidding <u> and inventing <mark> you could as well redefine <u> to be what <mark> is intended for -- roughly the same idea as for <i> and <b>. Clearly not all old HTML4 <i> / <b> / <u> match what the new HTML5 <i> / <b> / <mark> (Saturday, 29 January)
• [Bug 11912] New: HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, (Friday, 28 January)
• [Bug 11910] New: @id values in polyglot markup should be XML-valid (or not?) (Friday, 28 January)
• [Bug 11909] New: The principles of Polyglot Markup - validity? well-formed? DOM-equality? (Friday, 28 January)
• [Bug 11907] New: the event handler attributes in textTrack and TextTrackCue are marked as read only, and no other API such as addEventListener is indicated to set handlers. (Friday, 28 January)
• [Bug 11905] New: Escaping of "<" and "&" in Polyglot Markup (Friday, 28 January)
• [Bug 11904] New: <plaintext> and <xmp> in Polyglot Markup (Friday, 28 January)
• [Bug 11903] New: i think it'd be more convenient if explicit sections could be children of implicit sections, so you can use implicit sections in general and throw in an <aside> somewhere without breaking the outline. now if you want to throw in an <aside>, you need to ch (Friday, 28 January)
• [Bug 11902] New: Please Editor , my question is , how can I POST an HTML LIKE THIS ONE to my website { <a href="http://store.eSellerate.net/a.asp?c=0_SKU51516428610_AFL8676117870&at=PNZSRATE"><imgsrc="http://www.esellerate.net/images/banners/large_a.gif"border=0alt="Buy (Friday, 28 January)
• [Bug 11901] New: Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand. (Friday, 28 January)
• [Bug 11900] New: it would be nice to specify a range for the lineWidth, eg, [1, 5], which means that the line starts at width 1, and gradually moves to width 5 at the end point (Friday, 28 January)
• [Bug 11896] New: html-letter.pdf appears truncated (Thursday, 27 January)
• [Bug 11895] New: Make Downloads more reliable by specifying checksums (Thursday, 27 January)
• [Bug 11893] New: define lexical processing models for ARIA attributes (Thursday, 27 January)
• [Bug 11892] New: explicitly state that ARIA states and properties are formal/normative HTML attributes (Thursday, 27 January)
• [Bug 11891] New: add role attribute to list of global attributes and add definition for it (Thursday, 27 January)
• [Bug 11890] New: Sometimes we need a pixel(x,y) method. createImageData(1,1) anj put it is slow. javascript is not as fast as c/c++ (Thursday, 27 January)
• [Bug 11889] New: The text here says that an input element is always mutable and then says that “similarly” the user agent should not allow the user to modify the element's value or checkedness. The sense seems to be backwards. Not being allowed to modify something is (Thursday, 27 January)
• [Bug 11887] New: Remove useless input.valueAsNumber. Pretty much the same functionality can be actieved using parseFloat or parseInt (Thursday, 27 January)
• [Bug 11886] New: what is this? (Thursday, 27 January)
• [Bug 11884] New: HAVE_ALL_DATA would be good for when the UA has finished downloading the entire media file. Also, a "loaded" or "progressend" event should be fired so users can know when a file has finished buffering. (Thursday, 27 January)
• [Bug 11883] New: <?xml version="1.0" encoding="UTF-8"?> <!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> <title> :: Rupert Shr (Wednesday, 26 January)
• [Bug 11881] New: In step 9.3.1 missing "its" in "and (its) value is not the empty string" (Wednesday, 26 January)
• [Bug 11879] New: Is the setting and getting of the "original insertion mode" here needed. It seems like the "in table text" insertion mode can only be reached from the "in table" insertion mode, which would then always be the "original insertion mode"? (Wednesday, 26 January)
• [Bug 11877] New: text position (Wednesday, 26 January)
• [Bug 11876] New: text position (Wednesday, 26 January)
• [Bug 11875] New: text position (Wednesday, 26 January)
• [Bug 11873] New: typo: "Metadata" link (in para after the table) points to "auto" definition" (Wednesday, 26 January)
• [Bug 11872] New: Sugestion! Would be very important if in the input tag we have to complement the type="text", a atributte where we can tell what type of text we want to use, like number, tel, e-mail, date or text because the browser can care of the validation and the ma (Wednesday, 26 January)
• [Bug 11870] New: What about a minlength attribute? That would be useful in several situations. (Wednesday, 26 January)
• [Bug 11864] New: section "12 IANA considerations 12.1 text/html" suggests: "This registration is for community review and will be submitted to ...registration with IANA." I understand from this that it it intended to replace RFC 2854. If so I have a problem with the stat (Tuesday, 25 January)
• [Bug 11863] New: Should the text say something explicitly about successive br elements, commonly used for vertical spacing? (Tuesday, 25 January)
• [Bug 11861] New: Need to say to spin the event loop until all sync sections have run before running a new script to make resourse selection algorithm predictable. See http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-August/027878.html (Tuesday, 25 January)
• [Bug 11860] New: It might be interesting to allow an application to register itself as a (HTTP) proxy for an unknown scheme. (Tuesday, 25 January)
• [Bug 11858] New: fix title in ORIGIN reference (Tuesday, 25 January)
• [Bug 11857] New: getData() with no or too many arguments should throw (Tuesday, 25 January)
• [Bug 11856] New: what happens when nothing happens in the getData() algorithm? (Tuesday, 25 January)
• [Bug 11846] New: Hello, I read in the specifics that the <tt> tag was erased, probably due to the fact it is not short for a semantic label but is related to the graphical rendering. I think it is the only way to correctly markup an inline code, such as <pre> and <code> t (Monday, 24 January)
• [Bug 11842] New: Default track enabling for video elements seems to miss a qualifier (Monday, 24 January)
• [Bug 11840] New: <!DOCTYPE HTML> <html> <head> <meta name="description" content="Free Web tutorials" /> <meta name="keywords" content="HTML,CSS,XML,JavaScript" /> <meta name="author" content="StÃ¥le Refsnes" /> <meta charset="ISO-8859-1" /> </head> <body> <p>All meta info (Sunday, 23 January)
• [Bug 11839] New: window.opener needs to be writable, not readonly (Sunday, 23 January)
• [Bug 11838] New: In Gecko and Opera, at least, the "name" property on Window is replaceable. Should that be specced, or is it web-compatible enough to not make it replaceable? (Sunday, 23 January)
• [Bug 11837] New: remove Matroska example (Saturday, 22 January)
• [Bug 11833] New: Is the logic in 'valueAsNumber' overridable? For example, if the web page wants to accept a number formatted with commas "145,000" will that be allowed? (Friday, 21 January)
• [Bug 11832] New: Problem: providing that an input element of type checkbox has an itemprop, it's itemValue does not reflect the checked state of the element. The same could be said of other input elements or form elements. The common sense notion of an element's value isn (Friday, 21 January)
• [Bug 11831] New: hey babe i miss you so much :(( (Friday, 21 January)
• [Bug 11829] New: parts of default stylesheet setting unicode-bidi and direction should be normative (Friday, 21 January)
• [Bug 11828] New: Drop hgroup completely until more research has been conducted (Friday, 21 January)
• [Bug 11826] New: Your leading nav element has no title, thus is in contradiction to the proposal. (Thursday, 20 January)
• [Bug 11822] New: applet[align=bottom], embed[align=bottom], iframe[align=bottom], img[align=bottom], input[type=image][align=bottom], object[align=bottom] should not have vertical-align:baseline, but bottom (Thursday, 20 January)
• [Bug 11820] New: du huensohn lass mich bearbeiten you are motherfucker (Thursday, 20 January)
• [Bug 11819] New: var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); (Thursday, 20 January)
• [Bug 11817] New: Copyright should go from 2004 to 2011 now. (Wednesday, 19 January)
• [Bug 11816] New: Link broken: www.whatwg.org/specs/web-apps/current-work/html5-letter.pdf (Wednesday, 19 January)
• [Bug 11815] New: should add something about /favicon.ico too (Wednesday, 19 January)
• [Bug 11814] New: Pause on exit is not much use if the goal is to read the caption or display it using TTS since the caption has ceased to be relevant. Pause on entry might be more helpful (Wednesday, 19 January)
• [Bug 11812] New: The align attribute on the td and th elements should be conforming (Wednesday, 19 January)
• [Bug 11807] New: <HTML> <HEAD> <TITLE>SISTEMUL PERIODIC AL ELEMENTELOR</TITLE> </HEAD> <BODY> <CENTER> <H2>Sistemul periodic al elementelor (Tabelul periodic al lui Mendeleev).</H2> <table cellpadding="6" cellspacing="2"> <TR> <TD BGCOLOR=#FFAAFF align="center" title="Hid (Wednesday, 19 January)
• [Bug 11804] New: oh nonon onono non onono nonono nono nononono nonon onono nononononononononononononononononono (Wednesday, 19 January)
• [Bug 11798] New: It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Wednesday, 19 January)
• [Bug 11797] New: <richtext> </richtext> This will provide a default rich text widget which is scriptable and should also support the Rich Text Format (RTF) Default widget implementation should be a text area with richtext controls above it. This will enable browsers to pr (Wednesday, 19 January)
• [Bug 11796] New: HTML5 SUGGESTIONS ------------------------------ This file contains suggestions of tags / features that can be added to HTML5. I sincerely hope that these features are added especially the file tag (<file></file>) which is the last I would write on. I hav (Tuesday, 18 January)
• [Bug 11794] New: We should handle the case of a bunch of required controls all being hidden at once — the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? (Tuesday, 18 January)
• [Bug 11793] New: Canvas layers: have multiple drawing layers inside the canvas 2d context, right now to achieve this you must have multiple stacked canvases which isn't optimal (Tuesday, 18 January)
• [Bug 11791] New: "margin-bottom;" should read "margin-bottom:" (Tuesday, 18 January)
• [Bug 11788] New: <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top"><img src="images/header.gi (Tuesday, 18 January)
• [Bug 11787] New: <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top"><img src="images/header.gi (Tuesday, 18 January)
• [Bug 11786] New: <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top"><img src="images/top_heade (Tuesday, 18 January)
• [Bug 11785] New: <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top" class="topimage"></td> (Tuesday, 18 January)
• [Bug 11784] New: <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top" class="topimage">&nbsp;</t (Tuesday, 18 January)
• [Bug 11783] New: <script> should continue the normative requirement chain to the spec that defines the format of the contents of the element (Tuesday, 18 January)
• [Bug 11782] New: The spec requires event handler content attributes to match ES5 FunctionBody, but has no similar requirement for <script> content. It probably should. (Tuesday, 18 January)
• [Bug 11781] New: "Event handler content attributes #event-handler-content-attributes Referenced in: 7.1.1 Introduction 7.1.6.1 Event handlers (2) (3) (4), when specified, must contain valid JavaScript code matching the FunctionBody production." might be wrong since it d (Tuesday, 18 January)
• [Bug 11780] New: <!DOCTYPE HTML> <html lang="ja"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, maximum-scale=1"> <title>札幌のカフェ｜CROSS ROAD cafe</title> <link rel="stylesheet" href="/common (Tuesday, 18 January)
• [Bug 11779] New: <!DOCTYPE HTML> <html lang="ja"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, maximum-scale=1"> <title>札幌のカフェ｜CROSS ROAD cafe</title> <link rel="stylesheet" href="/common (Tuesday, 18 January)
• [Bug 11778] New: downloadable font support missing (Monday, 17 January)
• [Bug 11777] New: I love the </sarcasm> reference down in the middle of the parsing rules :D. Please do not ever remove it. Thank you, everyone, for all of your hard work. (Monday, 17 January)
• [Bug 11775] New: Hello, I'm just writing a quick note to question the non-inclusion of the "feed" link type (rel="feed") which I remember coming across a few months ago. When I originally saw the new rel type, I was very glad to see that there was finally a way to specify (Monday, 17 January)
• [Bug 11774] New: what is a class ? (Monday, 17 January)
• [Bug 11773] New: Re: applet obsoleted It seems that the committee is being deliberately hostile to Java applets. This is based on the fact that, with the proposed change, it will no longer be possible to include an applet in such a way as to be compatible with all browse (Monday, 17 January)
• [Bug 11771] New: What is "also" in "a working group decision also from June 2010" in reference too? (Saturday, 15 January)
• [Bug 11768] New: all your base are belong to us (Saturday, 15 January)
• [Bug 11767] New: this comment line is a good idea, i appreciate. (Friday, 14 January)
• [Bug 11755] New: The introduction should be clearer about use cases best addressed by polyglot markup (Friday, 14 January)
• [Bug 11754] New: Should clearly indicate that Web authors don't need to bother to make their content polyglot if they don't know they have a use case (Friday, 14 January)
• [Bug 11753] New: Don't like "stating what he wishes to drag and what he wishes to drop". Surely you drop what you've dragged, and the question is "where to drop it"? (Friday, 14 January)
• [Bug 11752] New: With the itemscope - it seems unnecessary since it becomes redundant whenever there's an itemtype - so why not have itemtype="item" (Friday, 14 January)
• [Bug 11748] New: The "size" attribute is disallowed, but may be useful on input="file". IE, Firefox and Opera all implement it, allowing you to reliably change the size of the file path textbox (Webkit browsers don't use a textbox). Styling the file upload file using CSS, (Thursday, 13 January)
• [Bug 11746] New: Add video, object, img, input[type=image], embed, canvas { overflow: hidden; } since people don't expect these elements to overflow in combination with object-fit:cover (see https://bugs.webkit.org/show_bug.cgi?id=52103 ) (Thursday, 13 January)
• [Bug 11745] New: Feature request: element.replaceSelection(str) should change the text field's value by replacing the current selection with the provided string, which should then be the new selection. This is apparently supported well in IE's proprietary equivalent, and (Thursday, 13 January)
• [Bug 11744] New: setPixel (x,y, color)and getPixel(x,y) should be implemented. getPixel should return color value (Wednesday, 12 January)
• [Bug 11739] New: I would like to see a clearPath or clearStroke functions similar to clearRect but to clear lines, not just full rectangles (Tuesday, 11 January)
• [Bug 11737] New: Change content model of <hgroup> to single <hx> + zero or more <sh> (sub/suphead) elements (Tuesday, 11 January)
• [Bug 11736] New: On XAMPP audio didn't work, at least on Firefox 4 beta and Google Chrome. On audio tag demo sites it works thought :/ (Tuesday, 11 January)
• [Bug 11734] New: Document the special effect of dir=auto on <pre> and <textarea> (Tuesday, 11 January)
• [Bug 11732] New: <div itemscope itemtype="http://data-vocabulary.org/Product"> <span itemprop="brand">»Ý¼Ò</span> <span itemprop="name">¾­µä Ô°ÒÕ¼ô</span> <img itemprop="image" src="anvil_executive.jpg" /> <span itemprop="description">»Ý¼Ò¾­µäÔ°ÒÕ¼ô ÓëÆäÆÕͨ (Tuesday, 11 January)
• [Bug 11731] New: Replace <hgroup> element with a <subhead> element used as the child of the <hx> element (Tuesday, 11 January)
• [Bug 11729] New: Hello your text is wrong.Hello your text is wrong.Hello your text is wrong.Hello your text is wrong. (Tuesday, 11 January)
• [Bug 11728] New: Hello hahaha :) hahaha :) hahaha :) hahaha :) hahaha :) hahaha :) (Tuesday, 11 January)
• [Bug 11727] New: user agent stylesheet display: block (Monday, 10 January)
• [Bug 11726] New: user agent stylesheet display: block (Monday, 10 January)
• [Bug 11722] New: make 404 page redirect faster or not say "File Not Found" until redirect script has failed (Monday, 10 January)
• [Bug 11721] New: Typo: "unforseen". The quick brown fox jumped over the lazy dog. (Monday, 10 January)
• [Bug 11720] New: At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. (Monday, 10 January)
• [Bug 11719] New: hasAttribute() also needs lowercasing. (This is already correct in Web DOM Core) (Monday, 10 January)
• [Bug 11717] New: Element.removeAttribute() needs to lowercase its argument when used on an HTML element. (Don't add anything for removeAttributeNode.) (Monday, 10 January)
• [Bug 11714] New: Not a bug, but a suggestion — add an example like this: “Price: €99 <small>(VAT included)</small>” (Monday, 10 January)
• [Bug 11712] New: typo: "labeld" should be "labeled" (Monday, 10 January)
• [Bug 11711] New: What about sandboxed XHTML ? (Monday, 10 January)
• [Bug 11709] New: People evaluating this spec should be allowed to download parts of it and go through them offline, in their favorite reading device. I'm currently interested in chapters 5 and 6, but I had to go to all sorts of trouble to get those in my iPad. Please prov (Sunday, 9 January)
• [Bug 11706] New: Why -00:00 instead of +00:00 when time zone is UTC? (Sunday, 9 January)
• [Bug 11705] New: Why does the definition of "middle" differ from the one in SVG 1.1 10.9.2? (Sunday, 9 January)
• [Bug 11699] New: When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define (Saturday, 8 January)
• [Bug 11695] New: import java.util.*; public class GeneralCalculation { static Scanner reader = new Scanner(System.in); public static void main(String[] args) { int Spearman, Slinger, Swordman, Planx, Archer, Sniper, Giro, Giant, Bomber, Ram, Catapult, Mortar, Doctor, Cook (Friday, 7 January)
• [Bug 11694] New: "best representation" does not define how to normalize decimal part of second (Friday, 7 January)
• [Bug 11690] New: "need a date" not xreffed (Friday, 7 January)
• [Bug 11688] New: Please add a note about loading appcache master entries that are listed in NETWORK section (Friday, 7 January)
• [Bug 11687] New: Make the non-normative parts of the definition of "application cache" into notes, to not mislead people into thinking they're normative. Only the list of what's in an appcache is normative here. (Friday, 7 January)
• [Bug 11678] New: <input type='email' multiple> should have the last comma stripped or being valid with a ending comma (Thursday, 6 January)
• [Bug 11677] New: <input type=hidden> shouldn't set framesetOk to false (Thursday, 6 January)
• [Bug 11674] New: really awesome! good job, dudes! (Wednesday, 5 January)
• [Bug 11671] New: Input Elements with state color and range and their attributes. (Wednesday, 5 January)
• [Bug 11670] New: "The setTransform(a, b, c, d, e, f) method must [...] invoke the transform(a, b, c, d, e, f) method" - so if I set CanvasRenderingContext2D.prototype.transform=function(){alert()}, then calling setTransform would trigger the alert? Probably this shouldn't (Wednesday, 5 January)
• [Bug 11668] New: Make the following note into a security warning: "It is possible that the output of this algorithm, if parsed with an HTML parser, will not return the original tree structure." and add an example of an attack (ack Eduardo Vela Nava) (Tuesday, 4 January)
• [Bug 11666] New: The value sanitisation algorithm should be clear that it sets the value property to the sanitized form. This is explicit in several cases but implicit in several cases. (Tuesday, 4 January)
• [Bug 11663] New: "non-shortest form" is more established than "overlong form" (Tuesday, 4 January)
• [Bug 11657] New: My worry is that this doesn't cover all the different kinds of textual transformations. Yes, it does cover obliqueness and weight, it does not cover letter spacing and other textual attributes that may be of some use to developers. (Tuesday, 4 January)
• [Bug 11647] New: Use exactly 2 digits for hours in WebVTT timestamps (Sunday, 2 January)
• [Bug 11646] New: step 13: copypasta in "the character at position is not a U+003A COLON character" (Sunday, 2 January)
• [Bug 11645] New: "may not be useful to everyone" misuses RFC2119 in a note (Sunday, 2 January)
• [Bug 11644] New: There are three occurrences of 'codepoint' without the space. (Sunday, 2 January)
• [Bug 11643] New: step 19: value4 cannot be greater than 999 (Sunday, 2 January)
• [Bug 11642] New: copypasta with "the five character string" and odd escape strings (Sunday, 2 January)
• [Bug 11636] New: sandox="allow-same-orgin" not work, or where got working example? j,sandrakumaran3@gmail.com (Saturday, 1 January)
• [Bug 11633] New: rm "does" in step 7 "but does the first elevent characters do not exactly equal" (Saturday, 1 January)

Charles McCathieNevile

• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: An HTML5 logo (Friday, 21 January)

Chris Adams

• Re: An HTML5 logo (Wednesday, 19 January)

Chris Double

• Re: Lifetime of new Audio() (Monday, 31 January)

Clair Dunn

• HTML5 logo: again-still (Wednesday, 19 January)

Dailey, David P.

• RE: HTML 5 (sic) and A11y (Monday, 24 January)
• RE: script execution corner case: timing of running a script created from a javascript: URL inside an IFRAME (Wednesday, 19 January)
• RE: An HTML5 logo (Tuesday, 18 January)

David Singer

• Re: ISSUE-142 (poster-alt): Chairs Solicit Proposals (Wednesday, 26 January)

Dean Leigh

• RE: hgroup: a possible alternative (Thursday, 13 January)
• RE: hgroup: a possible alternative (Wednesday, 12 January)
• RE: hgroup: a possible alternative (Wednesday, 12 January)
• RE: hgroup: a possible alternative (Wednesday, 12 January)
• RE: hgroup: a possible alternative (Tuesday, 11 January)

Doug Jones

• Fwd: ISSUE-130 table-layout - Chairs Solicit Alternate Proposals or Counter-Proposals (Friday, 14 January)
• Re: ISSUE-130 table-layout - Chairs Solicit Alternate Proposals or Counter-Proposals (Friday, 14 January)
• Fwd: ISSUE-130 table-layout - Chairs Solicit Alternate Proposals or Counter-Proposals (Friday, 14 January)
• Re: hgroup: a possible alternative (Monday, 10 January)

Edward O'Connor

• Re: ACTION-201 (was: {agenda} HTML WG Telecon 2010-01-20) (Wednesday, 19 January)
• Re: {agenda} HTML WG Telecon 2010-01-20: status of actions, calls; task force reports (Tuesday, 18 January)

Eihab Ibrahim

• Re: HTML 5 (sic) and A11y (Monday, 24 January)

Eliot Graff

• RE: Review on Polyglot Markup Draft (Wednesday, 26 January)

Frank Olivier

• RE: ISSUE-146 (video-content-muted): Chairs Solicit Proposals (Tuesday, 25 January)

Hallvord R. M. Steen

• script execution corner case: timing of running a script created from a javascript: URL inside an IFRAME (Wednesday, 19 January)

Haymo Meran

• contenteditable caret: request to more details (Monday, 17 January)

Henri Sivonen

• Re: ISSUE-144 (conforming-u): Chairs Solicit Proposals (Wednesday, 26 January)
• Re: ISSUE-144 (conforming-u): Chairs Solicit Proposals (Tuesday, 25 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Monday, 24 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Monday, 24 January)
• Withdrawal of ISSUE-128 (Saturday, 22 January)
• Re: script execution corner case: timing of running a script created from a javascript: URL inside an IFRAME (Thursday, 20 January)
• Re: Media TextFormats Accessibility Comparison Summary Released (Thursday, 6 January)
• Re: Media TextFormats Accessibility Comparison Summary Released (Monday, 3 January)
• Running heuristic encoding detection (Monday, 3 January)

Ian Hickson

• Re: ISSUE-144 (conforming-u): Chairs Solicit Proposals (Wednesday, 26 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Sunday, 23 January)
• Re: ISSUE-146 (video-content-muted): Chairs Solicit Proposals (Saturday, 22 January)
• Re: DataTransfer interface and items (Thursday, 20 January)
• ISSUE-120 CP (Wednesday, 19 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Wednesday, 19 January)
• Re: CfC: close ISSUE-126 charset-vs-backslashes by amicable resolution (Wednesday, 19 January)
• Re: CfC: close ISSUE-126 charset-vs-backslashes by amicable resolution (Wednesday, 19 January)
• Re: ISSUE-155 table-border: Chairs Solicit Proposals (Tuesday, 18 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Tuesday, 18 January)
• Re: CfC: close ISSUE-126 charset-vs-backslashes by amicable resolution (Tuesday, 18 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Tuesday, 18 January)
• Re: CfC: close ISSUE-119 rel-repetition by amicable resolution (Tuesday, 18 January)
• ISSUE-139 no-change CP (Tuesday, 18 January)
• ISSUE-129 CCP (Monday, 17 January)
• Re: Change Proposal for ISSUE-138, was: ISSUE-138 (mutate-action): Chairs Solicit Proposals (Wednesday, 12 January)
• Re: Change Proposal for ISSUE-138, was: ISSUE-138 (mutate-action): Chairs Solicit Proposals (Wednesday, 12 January)

Ian Jacobs

• Re: An HTML5 logo (Wednesday, 26 January)
• Re: An HTML5 logo (Friday, 21 January)
• Re: An HTML5 logo (Friday, 21 January)
• Re: An HTML5 logo (Tuesday, 18 January)
• Re: An HTML5 logo (Tuesday, 18 January)

James Graham

• Re: rationale for inclusion of hgroup in html5? (Thursday, 27 January)
• Re: rationale for inclusion of hgroup in html5? (Thursday, 27 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• Re: hgroup: a possible alternative (Monday, 10 January)

Jeremy Keith

• Re: An HTML5 logo (Friday, 21 January)
• Re: An HTML5 logo (Wednesday, 19 January)
• Re: An HTML5 logo (Tuesday, 18 January)
• Re: An HTML5 logo (Tuesday, 18 January)

Jirka Kosek

• Re: rationale for inclusion of hgroup in html5? (Thursday, 27 January)
• Re: rationale for inclusion of hgroup in html5? (Thursday, 27 January)
• Re: rationale for inclusion of hgroup in html5? (Monday, 24 January)

John Foliot

• RE: ISSUE-142 (poster-alt): Chairs Solicit Proposals (Tuesday, 25 January)
• RE: ISSUE-142 (poster-alt): Chairs Solicit Proposals (Tuesday, 25 January)
• RE: ISSUE-142 (poster-alt): Chairs Solicit Proposals (Saturday, 22 January)

Jonas Sicking

• Re: Lifetime of new Audio() (Monday, 31 January)
• Re: CfC: close ISSUE-126 charset-vs-backslashes by amicable resolution (Wednesday, 19 January)
• Re: CfC: close ISSUE-126 charset-vs-backslashes by amicable resolution (Wednesday, 19 January)

Joshue O Connor

• Re: HTML 5 (sic) and A11y (Tuesday, 25 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• HTML 5 (sic) and A11y (Monday, 24 January)

Julian Reschke

• "the rel attribute nolonger describes the direction of a relationship" (Monday, 31 January)
• Change Proposal for ISSUE-148, was: ISSUE-148 (charset-detect): Chairs Solicit Proposals (Saturday, 29 January)
• Re: ISSUE-145 (codecs-vs-octet): Chairs Solicit Proposals (Thursday, 27 January)
• Re: ISSUE-126 CCP -- no special handling for backslash (Tuesday, 25 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Monday, 24 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Monday, 24 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Monday, 24 January)
• Revised Change Proposal for ISSUE-125, was: ISSUE-125 charset-vs-quotes - Chairs Solicit Alternate Proposals or Counter-Proposals (Sunday, 23 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Sunday, 23 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Sunday, 23 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Sunday, 23 January)
• removing "TrackerRequest" on other people's issues (Sunday, 23 January)
• Change Proposal for ISSUE-145, was: ISSUE-145 (codecs-vs-octet): Chairs Solicit Proposals (Saturday, 22 January)
• Microsoft, WebDAV, and XML namespaces, was: ISSUE-120 CP (Friday, 21 January)
• Re: CfC: close ISSUE-126 charset-vs-backslashes by amicable resolution (Wednesday, 19 January)
• Re: Change Proposal for ISSUE-126 (Wednesday, 19 January)
• Re: ISSUE-102 (meta-name-registry): Chairs Solicit Proposals (Tuesday, 18 January)
• Re: ISSUE-138 (mutate-action): Chairs Solicit Proposals (Monday, 17 January)
• Change Proposal for ISSUE-139, was: ISSUE-139 (ack-microdata): Chairs Solicit Proposals (Sunday, 16 January)
• Fwd: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard (Friday, 14 January)
• Re: Change Proposal for ISSUE-138, was: ISSUE-138 (mutate-action): Chairs Solicit Proposals (Thursday, 13 January)
• Re: Change Proposal for ISSUE-138, was: ISSUE-138 (mutate-action): Chairs Solicit Proposals (Wednesday, 12 January)
• Change Proposal for ISSUE-138, was: ISSUE-138 (mutate-action): Chairs Solicit Proposals (Wednesday, 12 January)
• Re: get rid of warning on editors draft (Thursday, 6 January)
• Re: get rid of warning on editors draft (Tuesday, 4 January)

Justin Anthony Knapp

• An inherent flaw in <canvas>? (Monday, 31 January)

Kang-Hao (Kenny) Lu

• Fwd: Re: ISSUE-144 (conforming-u): Chairs Solicit Proposals (Thursday, 27 January)
• Re: ISSUE-144 (conforming-u): Chairs Solicit Proposals (Thursday, 27 January)
• Re: ISSUE-144 (conforming-u): Chairs Solicit Proposals (Wednesday, 26 January)

Kornel Lesiński

• Re: Why hgroup? (Monday, 10 January)
• Re: Why hgroup? (Monday, 10 January)
• Re: Why hgroup? (Thursday, 6 January)

Lars Gunther

• Re: hgroup: a possible alternative - or drop completely (Friday, 21 January)
• Re: hgroup: a possible alternative (Thursday, 20 January)

Laura Carlson

• Re: Withdrawal of ISSUE-128 (Sunday, 30 January)
• Re: ISSUE-129 CCP - copied for review and comment (Tuesday, 18 January)
• Re: ISSUE-129 CCP (Monday, 17 January)
• Re: ISSUE-130 table-layout - Chairs Solicit Alternate Proposals or Counter-Proposals (Friday, 14 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)

Leif Halvard Silli

• Re: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)
• Re: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)
• Re: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)
• Re: rationale for inclusion of hgroup in html5? (Thursday, 27 January)
• Re: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)
• Re: Handling of non-escalated pre-Last Call bugs (Thursday, 27 January)
• Re: rationale for inclusion of hgroup in html5? (Thursday, 27 January)
• Re: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)
• Re: CfC: close ISSUE-128 figure-in-p by amicable resolution (Wednesday, 26 January)
• Re: ISSUE-141 dl-dialog: Chairs Solicit Proposals (Wednesday, 19 January)
• Re: ISSUE-155 table-border: Chairs Solicit Proposals (Wednesday, 19 January)
• Re: Change proposal for HTML WG ISSUE-140: Conformance terminology when applicable specifications are used (Tuesday, 18 January)
• Re: An HTML5 logo (Tuesday, 18 January)
• Re: ISSUE-130 table-layout - Chairs Solicit Alternate Proposals or Counter-Proposals (Saturday, 15 January)
• Re: ISSUE-130 table-layout - Chairs Solicit Alternate Proposals or Counter-Proposals (Friday, 14 January)
• Re: ISSUE-130 table-layout - Chairs Solicit Alternate Proposals or Counter-Proposals (Friday, 14 January)
• RE: hgroup: a possible alternative (Wednesday, 12 January)
• RE: hgroup: a possible alternative (Wednesday, 12 January)
• RE: hgroup: a possible alternative (Wednesday, 12 January)
• Re: hgroup: a possible alternative (Wednesday, 12 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• RE: hgroup: a possible alternative (Tuesday, 11 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• Re: Why hgroup? (Tuesday, 11 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• Re: Why hgroup? (Sunday, 9 January)
• Re: Why hgroup? (Saturday, 8 January)
• Re: Why hgroup? (Saturday, 8 January)
• Re: Running heuristic encoding detection (Monday, 3 January)

Leonard Rosenthol

• RE: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)

Maciej Stachowiak

• Re: removing "TrackerRequest" on other people's issues (Wednesday, 26 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: script execution corner case: timing of running a script created from a javascript: URL inside an IFRAME (Wednesday, 19 January)
• Re: clarification requested on january 19 cut off for escalating pre last call bugs (Thursday, 13 January)
• ISSUE-130 table-layout - Chairs Solicit Alternate Proposals or Counter-Proposals (Thursday, 13 January)
• ISSUE-127 link-type-flags - Chairs Solicit Alternate Proposals or Counter-Proposals (Thursday, 13 January)
• ISSUE-150 code-point-verbosity: Chairs Solicit Proposals (Thursday, 13 January)
• Re: Change Proposal for ISSUE-138, was: ISSUE-138 (mutate-action): Chairs Solicit Proposals (Wednesday, 12 January)
• Re: hgroup: a possible alternative (Monday, 10 January)
• Re: Media TextFormats Accessibility Comparison Summary Released (Thursday, 6 January)
• Re: CfC: Publish eight heartbeat drafts as WDs (Thursday, 6 January)

Manu Sporny

• New HTML+RDFa 1.1 Working Draft published (Wednesday, 12 January)

Noah Mendelsohn

• Resubmission of Change proposal for HTML WG ISSUE-140: Conformance terminology when applicable specifications are used (Wednesday, 19 January)
• Re: Change proposal for HTML WG ISSUE-140: Conformance terminology when applicable specifications are used (Wednesday, 19 January)
• Change proposal for HTML WG ISSUE-140: Conformance terminology when applicable specifications are used (Tuesday, 18 January)

Ojan Vafai

• Re: script execution corner case: timing of running a script created from a javascript: URL inside an IFRAME (Wednesday, 19 January)

Othmane Benyoucef

• Proposal about more organizing the procedure of collaboration (Monday, 17 January)

Paul Cotton

• RE: request to re-open issue 133 due to submission of a change prposal. (Monday, 31 January)
• RE: CfC: close ISSUE-128 figure-in-p by amicable resolution (Thursday, 27 January)
• RE: Handling of non-escalated pre-Last Call bugs (Thursday, 27 January)
• CfC: close ISSUE-128 figure-in-p by amicable resolution (Wednesday, 26 January)
• Handling of non-escalated pre-Last Call bugs (Wednesday, 26 January)
• RE: Issue 129 counter proposal (Friday, 21 January)

Philip Jägenstedt

• Re: ISSUE-145 (codecs-vs-octet): Chairs Solicit Proposals (Thursday, 27 January)
• Re: ISSUE-125 CCP -- change the "willful violation" note -- rev 1 (Thursday, 27 January)
• Re: ISSUE-145 (codecs-vs-octet): Chairs Solicit Proposals (Sunday, 23 January)
• Re: ISSUE-151 (whatwg-references): Chairs Solicit Proposals (Saturday, 22 January)
• Re: ISSUE-146 (video-content-muted): Chairs Solicit Proposals (Saturday, 22 January)
• Re: ISSUE-142 (poster-alt): Chairs Solicit Proposals (Saturday, 22 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)

Philip Taylor

• Re: Change Proposal for ISSUE-126 (Wednesday, 19 January)

Philippe Le Hegaret

• RE: An HTML5 logo (Tuesday, 18 January)
• An HTML5 logo (Tuesday, 18 January)

Richard Ishida

• Fwd: [Bug 11829] New: parts of default stylesheet setting unicode-bidi and direction should be normative (Friday, 21 January)

Sam Ruby

• Re: ISSUE-145 (codecs-vs-octet): Chairs Solicit Proposals (Thursday, 27 January)
• Re: ISSUE-144 (conforming-u): Chairs Solicit Proposals (Thursday, 27 January)
• Re: ISSUE-144 (conforming-u): Chairs Solicit Proposals (Wednesday, 26 January)
• Re: ISSUE-125 CCP -- change the "willful violation" note (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Monday, 24 January)
• Re: review of hgroup element prior to last call. (Sunday, 23 January)
• Re: ISSUE-161 accessibility-api-mapping: Chairs Solicit Proposals (Saturday, 22 January)
• ISSUE-161 accessibility-api-mapping: Chairs Solicit Proposals (Saturday, 22 January)
• Re: ISSUE-160 menuless-commands: Chairs Solicit Proposals (Saturday, 22 January)
• ISSUE-160 menuless-commands: Chairs Solicit Proposals (Saturday, 22 January)
• ISSUE-158 object-content-model: Chairs Solicit Proposals (Saturday, 22 January)
• ISSUE-157 image-map-spec: Chairs Solicit Proposals (Saturday, 22 January)
• Re: Issue 129 counter proposal (Friday, 21 January)
• ISSUE-156 permit-close-tag: Chairs Solicit Proposals (Thursday, 20 January)
• Re: Resubmission of Change proposal for HTML WG ISSUE-140: Conformance terminology when applicable specifications are used (Wednesday, 19 January)
• Re: ISSUE-141 dl-dialog: Chairs Solicit Proposals (Wednesday, 19 January)
• Re: ISSUE-155 table-border: Chairs Solicit Proposals (Wednesday, 19 January)
• ACTION-201 (was: {agenda} HTML WG Telecon 2010-01-20) (Wednesday, 19 January)
• ISSUE-131 caret-location-API: Chairs Solicit Proposals (Tuesday, 18 January)
• ISSUE-155 table-border: Chairs Solicit Proposals (Tuesday, 18 January)
• ISSUE-152 multitrack-media-resources: Chairs Solicit Proposals (Tuesday, 18 January)
• Re: Change proposal for HTML WG ISSUE-140: Conformance terminology when applicable specifications are used (Tuesday, 18 January)
• Re: CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Tuesday, 18 January)
• CfC: close ISSUE-126 charset-vs-backslashes by amicable resolution (Tuesday, 18 January)
• CfC: close ISSUE-125 charset-vs-quotes by amicable resolution (Tuesday, 18 January)
• CfC: close ISSUE-119 rel-repetition by amicable resolution (Tuesday, 18 January)
• Re: ISSUE-143 remove-s: Chairs Solicit Proposals (Tuesday, 18 January)
• Re: ISSUE-141 dl-dialog: Chairs Solicit Proposals (Tuesday, 18 January)
• Correction: CfC: close ISSUE-138 (mutate-action) by amicable resolution (Monday, 17 January)
• Re: ISSUE-138 (mutate-action): Chairs Solicit Proposals (Monday, 17 January)
• Re: ISSUE-136 (remove-small): Chairs Solicit Proposals (Monday, 17 January)
• Re: ISSUE-134 (tag-states): Chairs Solicit Proposals (Monday, 17 January)
• ISSUE-151 (whatwg-references): Chairs Solicit Proposals (Wednesday, 5 January)
• ISSUE-149 (polyglot-examples): Chairs Solicit Proposals (Wednesday, 5 January)
• ISSUE-147 (playbackrate-undefined): Chairs Solicit Proposals (Wednesday, 5 January)
• ISSUE-148 (charset-detect): Chairs Solicit Proposals (Wednesday, 5 January)

Silvia Pfeiffer

• Re: ISSUE-142 (poster-alt): Chairs Solicit Proposals (Tuesday, 25 January)
• Re: Media TextFormats Accessibility Comparison Summary Released (Thursday, 6 January)
• Re: Media TextFormats Accessibility Comparison Summary Released (Thursday, 6 January)

Simon Pieters

• Re: rationale for inclusion of hgroup in html5? (Thursday, 27 January)
• Re: DOM comments inside a <style> element (Monday, 3 January)

Stephen Stewart

• Re: Why hgroup? (Friday, 7 January)

Steve Axthelm

• Re: rationale for inclusion of hgroup in html5? (Monday, 24 January)

Steve Faulkner

• hgroup poll wiki page (Monday, 31 January)
• request to re-open issue 133 due to submission of a change prposal. (Saturday, 29 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: rationale for inclusion of hgroup in html5? (Monday, 24 January)
• Re: rationale for inclusion of hgroup in html5? (Monday, 24 January)
• rationale for inclusion of hgroup in html5? (Sunday, 23 January)
• Re: review of hgroup element prior to last call. (Sunday, 23 January)
• review of hgroup element prior to last call. (Sunday, 23 January)
• RE: Issue 129 counter proposal (Friday, 21 January)
• restrictions and roles on table/tr/td/th appear in aria section in multipage version (Monday, 17 January)
• Re: ISSUE-129 CCP - copied for review and comment (Monday, 17 January)
• Re: ISSUE-129 CCP (Monday, 17 January)
• default roles of elements with accesskey set (Monday, 17 January)
• HGROUP revisited (Friday, 14 January)
• Re: clarification requested on january 19 cut off for escalating pre last call bugs (Thursday, 13 January)
• clarification requested on january 19 cut off for escalating pre last call bugs (Thursday, 13 January)
• RE: ISSUE-135: link-canvas-spec, Change Proposals due Jan 19 (Thursday, 13 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• Re: get rid of warning on editors draft (Sunday, 9 January)
• Re: Why hgroup? (Thursday, 6 January)
• Re: get rid of warning on editors draft (Thursday, 6 January)
• Summary element and outline algoritm (Thursday, 6 January)
• Why hgroup? (Thursday, 6 January)

Tab Atkins Jr.

• Re: "the rel attribute nolonger describes the direction of a relationship" (Monday, 31 January)
• Re: An inherent flaw in <canvas>? (Monday, 31 January)
• Re: "the rel attribute nolonger describes the direction of a relationship" (Monday, 31 January)
• Re: ISSUE-142 (poster-alt): Chairs Solicit Proposals (Tuesday, 25 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• Re: Why hgroup? (Tuesday, 11 January)
• Re: hgroup: a possible alternative (Monday, 10 January)
• Re: Why hgroup? (Monday, 10 January)
• Re: Why hgroup? (Monday, 10 January)

Tantek Çelik

• Re: "the rel attribute nolonger describes the direction of a relationship" (Monday, 31 January)
• Re: An HTML5 logo (Tuesday, 25 January)
• Re: An HTML5 logo (Friday, 21 January)

Toby Inkster

• Re: ISSUE-120 (rdfa-prefixes): Chairs Solicit Proposals (Friday, 21 January)
• Re: hgroup: a possible alternative (Tuesday, 11 January)
• hgroup: a possible alternative (Monday, 10 January)
• Re: DOM comments inside a <style> element (Saturday, 1 January)

Last message date: Monday, 31 January 2011 23:43:58 UTC