W3C home > Mailing lists > Public > public-html@w3.org > September 2012

Re: WHATWG patches staged for merge week 38

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Mon, 17 Sep 2012 19:39:37 +1000
Message-ID: <CAHp8n2kx_O2Jq+=trCaiWwfQ50iyYunEouPgOMdzUB00um7wFg@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: public-html <public-html@w3.org>
Thanks, will get to it with my Friday load.
Cheers,
Silvia.

On Mon, Sep 17, 2012 at 6:59 PM, Steve Faulkner
<faulkner.steve@gmail.com> wrote:
> Hi Silvia,
> have added comments to the source file.
>
> regards
> SteveF
>
> On 17 September 2012 09:42, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote:
>> Note that I'd preferably get the comments on the "source" file, since
>> the others are not relevant to us.
>>
>> Thanks,
>> Silvia.
>>
>> On Mon, Sep 17, 2012 at 6:41 PM, Silvia Pfeiffer
>> <silviapfeiffer1@gmail.com> wrote:
>>> Yes, that would be perfect. I can apply them selectively.
>>> Thanks,
>>> Silvia.
>>>
>>> On Mon, Sep 17, 2012 at 6:36 PM, Steve Faulkner
>>> <faulkner.steve@gmail.com> wrote:
>>>> Hi Silvia,
>>>>
>>>> I have been looking at the title attribute related changes
>>>> [https://github.com/w3c/html/compare/master...feature;whatwg_title]
>>>> some are relevant/appropriate, some are not, what is the best way to
>>>> provide feedback? I can add comments in github on the relevant lines
>>>> if that is ok?
>>>>
>>>>
>>>> regards
>>>> Steve
>>>>
>>>> On 15 September 2012 08:42, Steve Faulkner <faulkner.steve@gmail.com> wrote:
>>>>> hi silvia,
>>>>>
>>>>>> This branch has several patches that address the problem of using
>>>>>> @title for accessibility.
>>>>>>   I would like to get help to decide which parts to apply.
>>>>>>   Review here:
>>>>>>   https://github.com/w3c/html/compare/master...feature;whatwg_title
>>>>>
>>>>> I wil review the changes and provide feedback.
>>>>>
>>>>>>   This contains several updates to the WHATWG spec about the W3C spec.
>>>>>>   I think it can be applied safely without impact on the W3C spec,
>>>>>>   but we can also ignore it.
>>>>>>   Review here:
>>>>>>   https://github.com/w3c/html/compare/master...feature;whatwg_cleanup
>>>>>
>>>>> I strongly suggest that the details about the differences between the
>>>>> W3C spec and the WHATWG spec NOT be included as the language used is
>>>>> not neutral.
>>>>>
>>>>> I would instead suggest if the WG want to include information about
>>>>> the differences between the 2 specs it be drafted and reviewed by the
>>>>> WG.
>>>>>
>>>>> regards
>>>>> SteveF
>>>>>
>>>>> On 15 September 2012 04:22, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Today, I have managed to get to WHATWG patch 7290 (inc) [1].
>>>>>> This relates to WHATWG work done before the 28th August.
>>>>>>
>>>>>> (I was rather slow this week, because I made some mistakes last week
>>>>>> and there was a lot to plough through. I was more careful this week
>>>>>> and also created new bugs for patches that I thought were appropriate
>>>>>> to apply.)
>>>>>>
>>>>>> This week we have the following new branches for your feedback.
>>>>>>
>>>>>> PLEASE NOTE: you only ever have to look at the file called "source" to
>>>>>> give us feedback.
>>>>>>
>>>>>>
>>>>>> B1 (to land next week):
>>>>>> ==================
>>>>>>
>>>>>> * feature/whatwg_patches_week37_2012
>>>>>>   Review here:
>>>>>>   https://github.com/w3c/html/compare/master...feature;whatwg_patches_week37_2012
>>>>>>
>>>>>>   It will close the following bugs:
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=13226
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=16039
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18086
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17952
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18006
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17745
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18196
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18109
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18160
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17712
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18225
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18050
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18191
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18883
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18010
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18884
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18354
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18283
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18036
>>>>>>
>>>>>> * feature/whatwg_script
>>>>>>   Review here:
>>>>>>   https://github.com/w3c/html/compare/master...feature;whatwg_script
>>>>>>
>>>>>>   It will close the following bug:
>>>>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18886
>>>>>>
>>>>>>
>>>>>> B2 (undecided - feedback requested!):
>>>>>> =============================
>>>>>>
>>>>>> * feature/whatwg_title
>>>>>>   This branch has several patches that address the problem of using
>>>>>> @title for accessibility.
>>>>>>   I would like to get help to decide which parts to apply.
>>>>>>   Review here:
>>>>>>   https://github.com/w3c/html/compare/master...feature;whatwg_title
>>>>>>
>>>>>>   Relates to one bug:
>>>>>>   https://www.w3.org/Bugs/Public/show_bug.cgi?id=18875
>>>>>>
>>>>>>
>>>>>> B3 (postponed to HTML.next or not relevant):
>>>>>> ==================================
>>>>>>
>>>>>> *  feature/whatwg_canvas
>>>>>>   Review here:
>>>>>>   https://github.com/w3c/html/compare/master...feature;whatwg_canvas
>>>>>>
>>>>>>   This one had two new patches relating to bug:
>>>>>>   https://www.w3.org/Bugs/Public/show_bug.cgi?id=17284
>>>>>>
>>>>>> * feature/whatwg_cleanup
>>>>>>   This contains several updates to the WHATWG spec about the W3C spec.
>>>>>>   I think it can be applied safely without impact on the W3C spec,
>>>>>>   but we can also ignore it.
>>>>>>   Review here:
>>>>>>   https://github.com/w3c/html/compare/master...feature;whatwg_cleanup
>>>>>>
>>>>>> * feature/whatwg_microdata
>>>>>>   Review here:
>>>>>>   https://github.com/w3c/html/compare/master...feature;whatwg_microdata
>>>>>>
>>>>>>   I am planning to pull out a patch from this to branch for this bug:
>>>>>>   https://www.w3.org/Bugs/Public/show_bug.cgi?id=18882
>>>>>>
>>>>>>
>>>>>> Previous branches:
>>>>>> ===============
>>>>>>
>>>>>> We still have the following branches uncommitted that were not changed
>>>>>> this week:
>>>>>>
>>>>>> * feature/whatwg_websockets (waiting for feedback from Arthur Barstow)
>>>>>> * feature/whatwg_table (removes the issue-155 decision on border=1 - I
>>>>>> am not sure about the current state of this)
>>>>>> * feature/whatwg_window_find (drops an existing API)
>>>>>> * feature/whatwg_inert
>>>>>> * feature/whatwg_inputmode
>>>>>> * feature/whatwg_srcset
>>>>>>
>>>>>> For those who asked about the feature branch deletion strategy:
>>>>>> I have been deleting them when I landed them. And also I have been
>>>>>> landing them as individual patches, so there is basically no trace of
>>>>>> the committed feature branches left.
>>>>>> I have decided that from now on I will only land the
>>>>>> whatwg_patches_weekxxx branches as individual patches. Other branches
>>>>>> that I land, I will fast-forward, but land with a merge commit
>>>>>> ("--no-ff" option). I still want to delete the branches after landing,
>>>>>> because otherwise we clutter up the github branches list (it's long
>>>>>> enough already).
>>>>>>
>>>>>> Best Regards,
>>>>>> Silvia.
>>>>>>
>>>>>>
>>>>>> [1] http://html5.org/tools/web-apps-tracker?from=7289&to=7290
>>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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
>
>
>
> --
> 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 Monday, 17 September 2012 09:40:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 17 September 2012 09:40:31 GMT