W3C home > Mailing lists > Public > public-html@w3.org > January 2013

<article> in one-article document (was Re: Staged bugs & editorial fixes for HTML5.0, and staged WHATWG patches for HTML5.1)

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sat, 12 Jan 2013 20:30:01 +1100
Message-ID: <CAHp8n2n4ZDjOCUh0cU3r7e6_guA-rMOSLPYTJYO=Q0WeYEmd4w@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: public-html <public-html@w3.org>
Hi Steve,

The idea behind the non-normative explanation that a page that consists
only of "main content" doesn't need an <article> element makes sense. I
agree, however, that in view of the <main> element, that sentence needs
reformulation. Happy for any suggested wording.

Regards,
Silvia.

On Fri, Jan 11, 2013 at 8:39 PM, Steve Faulkner <faulkner.steve@gmail.com>wrote:

> Hi Silvia,
>
> unsure about this change in 5.1 Elaborate on <article> in one-article
> documents...
> https://github.com/w3c/html/commit/1f2ea9cb64042b8c52ed6761909107385e82690e
>
> Will file a bug on it and create a suggested patch, taking into account
> the use of <main> in this case.
>
> regards
> steve
>
>
> On 7 January 2013 23:47, Silvia Pfeiffer <silviapfeiffer1@gmail.com>wrote:
>
>> Hi all,
>>
>> This week the following WHATWG patches up to and inc commit 7637 [1] have
>> been cherry-picked into the W3C HTML specifications. This takes us to
>> WHATWG patches up to 5th January 2012, i.e. we are up-to-date.
>>
>> 1. Staged for HTML5.0 CR
>> ------------------------------------
>>
>> You can find the new patches staged for HTML5.0 CR at:
>> https://github.com/w3c/html/commits/editorial_fixes
>> (patches of 5th - 7th January)
>>
>> Apart from editorial (typos, missing links, unused definitions) fixes,
>> these close the following bugs:
>>
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=16826  (improve focus
>> ring wording)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=12154 (set definition
>> of <b> to bolder)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=16955 (explain why
>> Gregorian calendar is used)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=14709 (Clarify how
>> language codes are passed on to other tools)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=19207 (Update rt/rp
>> sections to match newer ruby section)
>>
>>
>>
>> 2. Cherry-picked into master for HTML5.1 FPWD
>> -----------------------------------------------------------------
>>
>> You can see the committed patches here:
>> https://github.com/w3c/html/commits/master
>> (patches for 5th - 7th January)
>>
>> If you see any patches there that should also be applied to HTML5.0 CR,
>> please register a bug.
>>
>> If you see any patches that should be moved to an extension spec and you
>> have a good technical reason (e.g. a competing spec), please speak up.
>>
>> The following new features have been introduced:
>> ======================================
>> (with Ian's patch numbers in brackets)
>> * support image sprites in drawImage() (7577, 7589) (not yet applied to
>> Canvas spec)
>> * introduce canvas 2D context fillRule attribute (7635) (not yet applied
>> to Canvas spec)
>> * dialog auto-center (7580)
>> * add credit card type to autocomplete list (7582)
>> * more ruby examples  (7583, 7584, 7585)
>> * allow use of bitmap fonts (7587)
>> * clarify storage events for localStorage (7592)
>> * sortable tables new feature  (7597, 7598, 7599, 7600,7601)
>> * replace <command> with <menuitem> - need to update aria mappings &
>> possibly remove from HTML5 spec, see
>> http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-December/038472.html(7602)
>> * make “submit” event bubble (7609, 7610)
>>
>> plus many more small feature improvements.
>>
>>
>> The following features have been removed:
>> ==================================
>> * remove <command>, see
>> http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-December/038472.html(7602)
>> * remove partial paths from <input file> (7578)
>> * Drop media queries on <a> and <area> - don't seem to be used or
>> implemented (7618)
>> * remove e4x JavaScript with ECMAScript for XML support (7625)
>>
>>
>> The following bugs have been closed:
>> ==================================
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=16826 (improve focus
>> ring wording)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=12154 (<b> to mean:
>> bolder)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=16955 (explain why
>> Gregorian calendar is used)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=17316 (provide example
>> with @seamless and inclusion for iframes)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=14709 (Clarify how
>> language codes are passed on to other tools)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=14540 (example with
>> only one <article> on page)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=19207 (Update rt/rp
>> sections to match newer ruby section)
>> * https://www.w3.org/Bugs/Public/show_bug.cgi?id=17787 (automatic sizing
>> of headings in <hgroup> if they follow <h1>)
>>
>>
>> These branches continue to be held back for extension specifications:
>>
>> * feature/whatwg_srcset:
>> https://github.com/w3c/html/compare/master...feature;whatwg_srcset
>>
>> * feature/whatwg_canvas_workers:
>> https://github.com/w3c/html/compare/master...feature;whatwg_canvas_workers
>>
>> I am planning to merge the canvas workers branch into master next week.
>> Let me know if there are objections.
>>
>> Best Regards,
>> Silvia.
>>
>>
>> [1] http://html5.org/tools/web-apps-tracker?from=7636&to=7637
>>
>
>
>
> --
> with regards
>
> Steve Faulkner
> Technical Director - TPG
>
> www.paciellogroup.com | www.HTML5accessibility.com |
> www.twitter.com/stevefaulkner
> HTML5: Techniques for providing useful text alternatives -
> dev.w3.org/html5/alt-techniques/
> Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
>
>
Received on Saturday, 12 January 2013 09:30:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 12 January 2013 09:30:50 GMT