Re: WHATWG cherry-pick

Oops. Thanks for fixing!
Silvia.
On 25 Nov 2013 01:43, "Steve Faulkner" <faulkner.steve@gmail.com> wrote:

> found a </div> was missing after latest changes, this broke multipage and
> lead to whole spec being enclosed in a div styled as an example :-)
>
> fixed.
>
> --
>
> Regards
>
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
>
>
> On 24 November 2013 03:51, Silvia Pfeiffer <silviapfeiffer1@gmail.com>wrote:
>
>> Hi all,
>>
>> I've just updated the HTML5.1 spec with the latest patches from the
>> feature/whatwg branch to get us up-to-date.
>>
>> Cheers,
>> Silvia.
>>
>> Here is the list of patches:
>>
>> 1.
>> https://github.com/w3c/html/commit/94faab079b26c82388849bdbffdf5b474adf43c2
>>    (WHATWG: 8311)
>>     [t] (1) Allow <input type=button value> to be translated, since
>> that value isn't submitted
>>     Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23842
>>     Affected topics: HTML
>>
>> 2.
>> https://github.com/w3c/html/commit/789dcb48cb098c04198588240eecdbb322d4b03a
>>     (WHATWG: 8310)
>>     [giow] (2) Prevent dead Blobs and Files from being cloned
>>     Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23417
>>     Affected topics: Canvas, DOM APIs
>>
>> 3.
>> https://github.com/w3c/html/commit/c01bd6d769b05ba95d1575d21dac4d6861fded2b
>>    (WHATWG: 8307)
>>     [giow] (2) Fix the rules on what 'Origin' header to use when
>> navigating to a resource in an <iframe>, <object>, <embed>, or <frame>
>> element, so that the latter two are not forgotten.
>>     Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23837
>>     Affected topics: HTML
>>
>> 4.
>> https://github.com/w3c/html/commit/e39262014f86761795d5e910d72069246dbcbe8b
>>     (WHATWG: 8306)
>>     [giow] (1) People apparently don't like it when the spec requires
>> things that are impossible to implement, go figure. (In this case,
>> synchronously detecting that one of the MessagePorts being Transferred
>> in the MessagePort message is actually the target of the message. You
>> can't necessarily know this synchronously, since if the port has been
>> shunted around between workers, you might only discover who the final
>> target actually is after the message has itself bounced between
>> threads for a while.)
>>     Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23685
>>     Affected topics: DOM APIs
>>
>>
>> Editorial changes:
>>
>> 1.
>> https://github.com/w3c/html/commit/87819a63c5f879a53600ab3631afa102336002a5
>>   (WHATWG: 8312)
>>    [e] (0) Mark areas that need updating for this bug (moving IDNA
>> references to URL standard references).
>>     Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23005
>>     Affected topics: Security
>>
>> 2.
>> https://github.com/w3c/html/commit/7a5b9e7cfe41ba6014e0c7304a5eb3416d48cb47
>>     (WHATWG: 8309)
>>     [e] (0) try to add a cross-reference at the dfn of 'do not apply'
>> to link people to where those terms are used
>>     Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23413
>>     Affected topics: DOM APIs, HTML
>>
>> 3.
>> https://github.com/w3c/html/commit/c75a745cae8b3c63cc9086f4f32466650546343e
>>    (WHATWG: 8308)
>>     [e] (0) Try to clarify the term 'line segments' with a
>> cross-reference.
>>     Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23761
>>     Affected topics: Canvas
>>
>>
>

Received on Sunday, 24 November 2013 22:43:25 UTC