Re: Patches merged or staged for week 50

Hi all,

This week, I am starting to cherry-pick patches from the WHATWG spec again.
Apologies for the lengthy delay.

Following a discussion on the public-html-admin list, I will list the new
features that have been introduced through cherry-picking patches. That
will give people an opportunity to object against the introduction of the
new feature if they have a good technical reason against it, such as a
competing specification. In this case, the patches will be removed from
master and moved to a feature branch so it can get handled as an extension
spec. Note that this has been the case for the @srcset specification.

A further result of the discussions was that editors will also apply
extension specifications to HTML5.1 that have reached FPWD and that have no
competing extension specification. An example of such an extension
specification is the <main> element and we have a bug requesting merger: .

Happy New Year from you friendly editor team. :-)


On Tue, Dec 18, 2012 at 9:24 AM, Silvia Pfeiffer

> Apologies - I'm moving house this week and have not been able to get to
> the next lot of patches and address the issues raised around this lot. I
> will make up for it next week.
> Silvia.
> On Fri, Dec 7, 2012 at 11:00 PM, Silvia Pfeiffer <
>> wrote:
>> Hi all,
>> This week the following WHATWG patches up to and inc commit 7569 [1] have
>> been merged into the W3C HTML specifications. This takes us to WHATWG
>> patches up to 5th December 2012.
>> 1. Staged for HTML5.0 CR
>> ------------------------------------
>> You can find the new patches staged for HTML5.0 CR at:
>> (patches for 7th December)
>> Closes the following pre-CR bugs:
>> (clarify <wbr>)
>> (extend encoding
>> sniffing)
>> 2. Merged into master for HTML5.1 FPWD
>> --------------------------------------------------------
>> I merged WHATWG patch up to and inc commit 7569 [1], which takes us to
>> 5th December 2012.
>> You can see the committed patches here:
>> (patches for 7th Dec)
>> 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, speak
>> up, too.
>> The following bugs have been closed:
>> (fullscreen
>> integration)
>> (clarify "cancel
>> navigation")
>> This one is fixed in HTML5.1, with a question whether to apply patches
>> back to the CR branch:
>> (video @poster
>> compatibility)
>> Other features that have been added include:
>> * crossorigin attribute on script
>> * add document.currentScript
>> These branches continue to be held back for extension specifications:
>> * feature/whatwg_srcset:
>> * feature/whatwg_canvas_workers:
>> I will address the feedback on last week's patches separately.
>> Best Regards,
>> Silvia.
>> [1]

Received on Sunday, 6 January 2013 06:22:24 UTC