Re: Patches merged or staged for week 50

I assume that by this you are asking to pull this specification out into a
separate extension spec to give it a chance to also still be included in
HTML5? I guess it needs somebody to write a rationale for why we need this
(at minimum it needs an abstract). Are you volunteering?

Regards,
Silvia.


On Sat, Dec 8, 2012 at 4:14 AM, Travis Leithead <
travis.leithead@microsoft.com> wrote:

>  Should:****
>
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=16709 (fullscreen
> integration)****
>
> be a separate extension spec? Seems like a good candidate for one...****
>
> ** **
>
> ** **
>
> *From:* Silvia Pfeiffer [mailto:silviapfeiffer1@gmail.com]
> *Sent:* Friday, December 7, 2012 4:00 AM
> *To:* public-html
> *Subject:* Patches merged or staged for week 50****
>
> ** **
>
> 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:
> https://github.com/w3c/html/commits/editorial_fixes
> (patches for 7th December)
>
> Closes the following pre-CR bugs:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=16001 (clarify <wbr>)
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18394 (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:
> https://github.com/w3c/html/commits/master
> (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:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=16709 (fullscreen
> integration)
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18291 (clarify "cancel
> navigation")
>
> This one is fixed in HTML5.1, with a question whether to apply patches
> back to the CR branch:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=15140 (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:
> 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 will address the feedback on last week's patches separately.
>
> Best Regards,****
>
> Silvia.
>
>
> [1] http://html5.org/tools/web-apps-tracker?from=7568&to=7569****
>
> ** **
>
> ** **
>