- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Sun, 9 Sep 2012 22:43:54 +1000
- To: Steve Faulkner <faulkner.steve@gmail.com>
- Cc: public-html <public-html@w3.org>
Hi Steve, Thanks for your feedback. That agrees with my initial reaction - thanks for confirming. I'll plan to move that branch to B3 where it can wait until there will be a HTML.next spec. Regards, Silvia. On Sun, Sep 9, 2012 at 9:50 PM, Steve Faulkner <faulkner.steve@gmail.com> wrote: > Hi Silvia, > > many thanks for your work! > >>* feature/whatwg_srcset > > This patch introduces the @srcset attribute on images. > > Review here: > >https://github.com/w3c/html/compare/master...feature;whatwg_srcset > > > Since the <picture> element is under active consideration by the WG > and there is no consensus on srcset or <picture> > > I would suggest not to add srcset at this time. > > > regards > SteveF > > On 9 September 2012 09:49, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: >> Hi all, >> >> Our Working Group is chartered to actively pursue convergence with the >> WHATWG specification [1]. >> >> As such, one of the tasks that the new editors of the W3C HTML >> specification have taken upon themselves is to work through the >> patches that Ian has been making to the WHATWG specification and >> successively merging them into the W3C specification where >> appropriate. >> >> Since we have moved to using GitHub [2] to manage the development of >> the specification, we are using a development model that is >> extensively based on branches [3], [4]. >> >> Over the last weeks, I have experimented with this approach and found >> it works well to help others review patches before landing them. >> >> Today I want to take this to the WG, so you can all get involved in >> helping review changes before they get in - and help me from merging >> features that we really want in HTML.next or that are not ok to be >> merged for any other reason. >> >> Every week, I will put together a set of new feature branches with >> commits from the WHATWG spec for review. >> >> These fall generally in these three classes: >> (B1) branches with fixes for typos or that resolve bugs in our bug >> tracker (i.e. we likely all appreciate that these should be applied). >> (B2) branches with features that are either new, or for which I don't >> know if we should merge them. >> (B3) branches/patches with features that we decided to hold back from >> HTML5 (also listed in [5]). >> >> Every Friday (Australian time) I will apply the feature branches from >> the previous week that I have announced will be applied the week >> before, or for which we have resolved through discussion during the >> week that we should apply them. >> >> At any time, you can find the list of current branches at [6]. >> >> >> Here is the list of branches that we have this week for your review: >> =================================================== >> >> Today, I have managed to get to WHATWG patch 7256 (inc) [7]. >> So, please do not complain about any patches that were made afterwards >> - I'll get to them eventually. >> I have only this far caught up with the WHATWG work before the 23rd August. >> >> B1 branches (i.e. branches/patches I will commit next week unless I >> hear otherwise): >> >> * feature/whatwg_patches >> This is the branch with the largest number of patches. >> These patches are all small-ish, mostly typo fixes or replies to >> small bug reports. >> You can reeview the patches here: >> https://github.com/w3c/html/compare/master...feature;whatwg_patches >> Click on "Files Changed" tab to see the change to the files themselves. >> You can even leave comments right there. >> >> * feature/whatwg_i18n >> This is a branch with changes to internationalization issues. >> Review here: >> https://github.com/w3c/html/compare/master...feature;whatwg_i18n >> Try clicking on the "..." in the commits to get more info. >> >> * feature/whatwg_ruby >> This is a branch with <ruby> examples. >> Review here: >> https://github.com/w3c/html/compare/master...feature;whatwg_ruby >> >> * feature/whatwg_tables >> This is a patch that deals with table borders. >> Review here: >> https://github.com/w3c/html/compare/master...feature;whatwg_tables >> >> * feature/whatwg_websockets >> This is a branch that relates to websockets. >> Review here: >> https://github.com/w3c/html/compare/master...feature;whatwg_websockets >> >> * feature/whatwg_window_find >> This is a patch that drops the window.find() legacy API. >> Review here: >> https://github.com/w3c/html/compare/master...feature;whatwg_window_find >> >> * feature/whatwg_fingerprinting >> This patch discusses user privacy vs user convenience & implications >> on fingerprinting. >> Review here: >> https://github.com/w3c/html/compare/master...feature;whatwg_fingerprinting >> >> >> B2 branches (i.e. branches I don't know if we should commit them): >> If you feel strongly about one of these branches either way >> (pro/contra commit), please speak up. >> >> * feature/whatwg_inert >> This patch clarifies 'inert' wrt focusability. >> Review here: >> https://github.com/w3c/html/compare/master...feature;whatwg_inert >> >> * feature/whatwg_inputmode >> This branch introduces several changes to form elements, including >> inputmode and autocomplete attributes. >> Review here: >> https://github.com/w3c/html/compare/master...feature;whatwg_inputmode >> >> * feature/whatwg_srcset >> This patch introduces the @srcset attribute on images. >> Review here: >> https://github.com/w3c/html/compare/master...feature;whatwg_srcset >> >> >> B3 branches (i.e. branches that we decided to keep back for HTML.next): >> >> * feature/whatwg_canvas >> This branch has several patches for new Canvas features, in >> particular HD versions for the ImageData API. >> Review here: >> https://github.com/w3c/html/compare/master...feature;whatwg_canvas >> >> >> Feedback will be welcome on list or directly in the feature branches. >> You will need a GitHub account to leave comments there. >> Please make statements for which you expect a discussion here on the >> mailing list, and only report trivial mistakes in GitHub, since only >> the editors will see the feedback on GitHub. >> >> Thanks for your patience and support in helping us get our extensive >> editing tasks done! >> >> Best Regards, >> Silvia. >> >> >> [1] http://www.w3.org/2007/03/HTML-WG-charter.html >> [2] https://github.com/w3c/html >> [3] https://github.com/nvie/gitflow >> [4] http://www.w3.org/QA/2012/09/the_flowing_standard.html (Robin's >> blog post on the issue) >> [5] https://github.com/w3c/html/blob/master/unmergedFromWHATWG >> [6] https://github.com/w3c/html/branches >> [7] http://html5.org/tools/web-apps-tracker?from=7255&to=7256 >> > > > > -- > 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 Sunday, 9 September 2012 12:44:44 UTC