<pimpbot> planet: Planet Opera: Choose Opera: Human HTML5 demo? <11http://my.opera.com/chooseopera/blog/show.dml/24903032>
<CIA-1> validator: 03Michael[tm] Smith <mike@w3.org> * 3b751270f499 r605 10syntax/relaxng/applications.rnc: Correct the broken checking of dropzone att. b=811
<CIA-1> validator: 03Michael[tm] Smith <mike@w3.org> * dc4d70a03fab r606 10syntax/relaxng/datatype/java/src/org/whattf/datatype/ (IriRef.java FunctionBody.java):
<CIA-1> validator: Force rhino to check for JS FunctionBody. b=812
<CIA-1> validator: Thanks to ar112 for the patch.
<CIA-1> html-spec: 03ianh@340c8d12-0b0e-0410-8428-c7bf67bfef74 * 2200d2575a13 r5788 10/ (index complete.html): [e] (0) minor edits
<pimpbot> bugmail: [Bug 11819] New: var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); <11http://lists.w3.org/Archives/Public/public-html-bugzilla/2011Jan/0640.html>
<pimpbot> bugmail: [Bug 11820] New: du huensohn lass mich bearbeiten you are motherfucker <11http://lists.w3.org/Archives/Public/public-html-bugzilla/2011Jan/0641.html>
<pimpbot> planet: ercimomweb: HTML5 logo has arrived <11http://openmediaweb.eu/2011/01/20/html5-logo-has-arrived/>
<pimpbot> bugmail: [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? <11http://lists.w3.org/Archives/Public/public-html-bugzilla/2011Jan/0642.html>
<pimpbot> bugmail: "[Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation?" (2 messages in thread) <11http://lists.w3.org/Archives/Public/public-html-bugzilla/2011Jan/0643.html>
<CIA-1> validator: 03Michael[tm] Smith <mike@w3.org> * 2e424c709c15 r607 10syntax/relaxng/datatype/java/src/org/whattf/datatype/IriRef.java: simplify something slightly
<pimpbot> bugmail: [Bug 11822] New: applet[align=bottom], embed[align=bottom], iframe[align=bottom], img[align=bottom], input[type=image][align=bottom], object[align=bottom] should not have vertical-align:baseline, but bottom <11http://lists.w3.org/Archives/Public/public-html-bugzilla/2011Jan/0644.html>
<pimpbot> planet: Bruce Lawson: Two cheers for the W3C’s HTML5 logo <11http://feedproxy.google.com/~r/html5doctor/~3/9u_yPQilLOc/>
<pimpbot> bugmail: [Bug 11819] var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); <11http://lists.w3.org/Archives/Public/public-html-bugzilla/2011Jan/0645.html>
<pimpbot> bugmail: "[Bug 11819] var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh);" (2 messages in thread) <11http://lists.w3.org/Archives/Public/public-html-bugzilla/2011Jan/0646.html>
<pimpbot> changes: sam: Call for proposals complete <11http://lists.w3.org/Archives/Public/public-html-diffs/2011Jan/0106.html>
<pimpbot> bugmail: [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? <11http://lists.w3.org/Archives/Public/public-html-bugzilla/2011Jan/0649.html> 4** [Bug 11797] <richtext> </richtext> This will provide a default rich text widget which is scriptable and should also
<pimpbot> bugmail: [Bug 11819] var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); <11http://lists.w3.org/Archives/Public/public-html-bugzilla/2011Jan/0650.html>
<rubys> trackbot, start meeting
<trackbot> Date: 20 January 2011
<scribe> ScribeNick: adrianba
<scribe> Scribe: Adrian Bateman
<pimpbot> Title: {agenda} HTML WG Telecon 2010-01-20: status of actions, calls; task force reports from Sam Ruby on 2011-01-18 (public-html-wg-announce@w3.org from January to March 2011) (at lists.w3.org)
<eliot> I hear both of you
ACTION-29?
<trackbot> ACTION-29 -- Philippe Le Hégaret to follow up on the idea of a free-software-compatible license for a note on HTML authoring -- due 2011-01-20 -- OPEN
<trackbot> http://www.w3.org/html/wg/tracker/actions/29
<pimpbot> Title: ACTION-29: Follow up on the idea of a free-software-compatible license for a note on HTML authoring - HTML Weekly Tracker (at www.w3.org)
mjs: if anything needed to be
reported, it would come from plh
... nothing to report at the moment from me
ISSUE-153?
<trackbot> ISSUE-153 -- link type "external" either not useful or underspecified -- raised
<trackbot> http://www.w3.org/html/wg/tracker/issues/153
<pimpbot> Title: ISSUE-153: link type "external" either not useful or underspecified - HTML Weekly Tracker (at www.w3.org)
ISSUE-154?
<trackbot> ISSUE-154 -- "sidebar" might not be a proper use of a link relation -- raised
<trackbot> http://www.w3.org/html/wg/tracker/issues/154
<pimpbot> Title: ISSUE-154: "sidebar" might not be a proper use of a link relation - HTML Weekly Tracker (at www.w3.org)
rubys: both of these will be last call issues since the bugs came after the cut-off
ISSUE-155?
<trackbot> ISSUE-155 -- make <table border="1" cellpadding="10" cellspacing="0"> conforming -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/155
<pimpbot> Title: ISSUE-155: make conforming - HTML Weekly Tracker (at www.w3.org)
rubys: call for proposals issued and received first change proposal
ISSUE-156?
<trackbot> ISSUE-156 -- Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment -- raised
<trackbot> http://www.w3.org/html/wg/tracker/issues/156
<pimpbot> Title: ISSUE-156: Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment - HTML Weekly Tracker (at www.w3.org)
rubys: opened since i sent the
agenda
... as we're getting close to the deadline i'll open a call for
proposals after the meeting
julian: i thought the last call cut off was in jan
rubys: the original deadline for
bugs was in oct
... doesn't mean we can't accept issues, etc but won't hold up
last call
ISSUE-119?
<trackbot> ISSUE-119 -- Certain relationships take on a special meaning when repeated; other solutions may be cleaner -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/119
<pimpbot> Title: ISSUE-119: Certain relationships take on a special meaning when repeated; other solutions may be cleaner - HTML Weekly Tracker (at www.w3.org)
ISSUE-125?
<trackbot> ISSUE-125 -- Requirement to break RFC 2616 compliance with respect to single quotes not needed for legacy content -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/125
<pimpbot> Title: ISSUE-125: Requirement to break RFC 2616 compliance with respect to single quotes not needed for legacy content - HTML Weekly Tracker (at www.w3.org)
ISSUE-126?
<trackbot> ISSUE-126 -- Requirement to break RFC 2616 compliance with respect to backslashes not needed for legacy content -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/126
<pimpbot> Title: ISSUE-126: Requirement to break RFC 2616 compliance with respect to backslashes not needed for legacy content - HTML Weekly Tracker (at www.w3.org)
rubys: these we have calls for amicable resolution and ongoing discussion on the mailing list
ISSUE-134?
<trackbot> ISSUE-134 -- Provide tablist and tab states for menu and command elements respectively -- closed
<trackbot> http://www.w3.org/html/wg/tracker/issues/134
<pimpbot> Title: ISSUE-134: Provide tablist and tab states for menu and command elements respectively - HTML Weekly Tracker (at www.w3.org)
ISSUE-136?
<trackbot> ISSUE-136 -- would the <small> element be better handled in CSS? -- closed
<trackbot> http://www.w3.org/html/wg/tracker/issues/136
<pimpbot> Title: ISSUE-136: would the element be better handled in CSS? - HTML Weekly Tracker (at www.w3.org)
rubys: both closed without prejudice as we are yet to receive a change proposal
ISSUE-138?
<trackbot> ISSUE-138 -- "mutate action" for issueing a GET request is misleading -- pending review
<trackbot> http://www.w3.org/html/wg/tracker/issues/138
<pimpbot> Title: ISSUE-138: "mutate action" for issueing a GET request is misleading - HTML Weekly Tracker (at www.w3.org)
rubys: change proposal received and call for amicable resolution based on this (change already made)
ISSUE-120?
<trackbot> ISSUE-120 -- Use of prefixes is too complicated for a Web technology -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/120
<pimpbot> Title: ISSUE-120: Use of prefixes is too complicated for a Web technology - HTML Weekly Tracker (at www.w3.org)
ISSUE-135?
<trackbot> ISSUE-135 -- put back direct link to the W3C version of the canvas 2d context spec -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/135
<pimpbot> Title: ISSUE-135: put back direct link to the W3C version of the canvas 2d context spec - HTML Weekly Tracker (at www.w3.org)
ISSUE-139?
<trackbot> ISSUE-139 -- HTML5 spec mentions Microdata in Acknowledgements -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/139
<pimpbot> Title: ISSUE-139: HTML5 spec mentions Microdata in Acknowledgements - HTML Weekly Tracker (at www.w3.org)
ISSUE-140?
<trackbot> ISSUE-140 -- clarify the applicability of the term "conforming document" in cases where "applicable specifications" had been used to augment or change the base HTML5 specification -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/140
<pimpbot> Title: ISSUE-140: clarify the applicability of the term "conforming document" in cases where "applicable specifications" had been used to augment or change the base HTML5 specification - HTML Weekly Tracker (at www.w3.org)
rubys: change proposal and
counter proposal for 139
... change proposal for 140
... nothing received for the others
ISSUE-142?
<trackbot> ISSUE-142 -- No alternative text description for video key frame (poster) -- raised
<trackbot> http://www.w3.org/html/wg/tracker/issues/142
<pimpbot> Title: ISSUE-142: No alternative text description for video key frame (poster) - HTML Weekly Tracker (at www.w3.org)
ISSUE-144?
<trackbot> ISSUE-144 -- <u> should be conforming -- raised
<trackbot> http://www.w3.org/html/wg/tracker/issues/144
<pimpbot> Title: ISSUE-144: should be conforming - HTML Weekly Tracker (at www.w3.org)
ISSUE-145?
<trackbot> ISSUE-145 -- use of "codecs" parameter -- raised
<trackbot> http://www.w3.org/html/wg/tracker/issues/145
<pimpbot> Title: ISSUE-145: use of "codecs" parameter - HTML Weekly Tracker (at www.w3.org)
ISSUE-146?
<trackbot> ISSUE-146 -- <video> should allow muted as a content attribute -- raised
<trackbot> http://www.w3.org/html/wg/tracker/issues/146
<pimpbot> Title: ISSUE-146: should allow muted as a content attribute - HTML Weekly Tracker (at www.w3.org)
rubys: all of these due jan 26
<Julian> we do have a proposal for ISSUE-135, right?
rubys: (correction - we did receive proposals on all items closing this week - next status will be issue a call for counter proposals)
ISSUE-138?
<trackbot> ISSUE-138 -- "mutate action" for issueing a GET request is misleading -- pending review
<trackbot> http://www.w3.org/html/wg/tracker/issues/138
<pimpbot> Title: ISSUE-138: "mutate action" for issueing a GET request is misleading - HTML Weekly Tracker (at www.w3.org)
ISSUE-119?
<trackbot> ISSUE-119 -- Certain relationships take on a special meaning when repeated; other solutions may be cleaner -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/119
<pimpbot> Title: ISSUE-119: Certain relationships take on a special meaning when repeated; other solutions may be cleaner - HTML Weekly Tracker (at www.w3.org)
ISSUE-125?
<trackbot> ISSUE-125 -- Requirement to break RFC 2616 compliance with respect to single quotes not needed for legacy content -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/125
<pimpbot> Title: ISSUE-125: Requirement to break RFC 2616 compliance with respect to single quotes not needed for legacy content - HTML Weekly Tracker (at www.w3.org)
ISSUE-126?
<trackbot> ISSUE-126 -- Requirement to break RFC 2616 compliance with respect to backslashes not needed for legacy content -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/126
<pimpbot> Title: ISSUE-126: Requirement to break RFC 2616 compliance with respect to backslashes not needed for legacy content - HTML Weekly Tracker (at www.w3.org)
rubys: calls for consensus on all these (as mentioned earlier in the agenda)
ISSUE-131?
<trackbot> ISSUE-131 -- Should we add a caret location API to canvas, or is the focus API sufficient? -- raised
<trackbot> http://www.w3.org/html/wg/tracker/issues/131
<pimpbot> Title: ISSUE-131: Should we add a caret location API to canvas, or is the focus API sufficient? - HTML Weekly Tracker (at www.w3.org)
ISSUE-152?
<trackbot> ISSUE-152 -- Handling of additional tracks of a multitrack audio/video resource -- raised
<trackbot> http://www.w3.org/html/wg/tracker/issues/152
<pimpbot> Title: ISSUE-152: Handling of additional tracks of a multitrack audio/video resource - HTML Weekly Tracker (at www.w3.org)
ISSUE-155?
<trackbot> ISSUE-155 -- make <table border="1" cellpadding="10" cellspacing="0"> conforming -- open
<trackbot> http://www.w3.org/html/wg/tracker/issues/155
<pimpbot> Title: ISSUE-155: make conforming - HTML Weekly Tracker (at www.w3.org)
rubys: all due feb 21
... i also plan to make a call for change proposals on
ISSUE-156 after this call
rubys: None
krisk: met as planned last
tuesday
... talked a little about the canvas test approval
... move the vast majority into the approved folder
... group also talked about the upcoming server name change
that plh and the w3c team are working on
... some discussion about php support and that it would be best
for plh to work with webapps xhr as a good sample for using
php
... group meets again this coming tuesday
... going to start looking at submitted audio and video cases -
there about 200 of these
... need to get consensus and we can move these to the approved
folder too
... that's it - any questions?
janina: top news item is that
we've scheduled a f2f mar 19/20 in san diego
... there is an annual conference for a11y and many people will
be there anyway
... also ahead of an important date in LC timeline
... expect to close issues there
... will extend an invitation to wider community than typical
wed meeting
... moving forward - getting lots of bugs dealt with
... in some cases closed, in other cases more work to do but
making good progress
... mike and i are continuing to emphasise that we need to be
closing and getting to consensus on change proposals
... good activity on aria mappings - good feedback from the
editor
... healthy interaction
... canvas is making progress and getting more vendors
involved
... in media we were talking about video poster but we had
under specified the user requirement and we are unclear about
how to resolve on the engineering side
... we need to get a bug filed here and find out if there are
potential issues for the spec or if it us an author issue
... this is related to autoplay of media that can be an a11y
issue
... as a screen reader if something starts playing and i can't
control it that is a problem
... we're not accustomed to dealing with media requirements and
so we missed this
MikeSmith: one other thing i
wanted to mention about the TF call
... we have a bug triage team for a few months going through
the open bugs relating to a11y
... and closing and commenting and making recommendations
... the decision policy doesn't seem to give complete guidance
for bugs that have been verified for more than two weeks
... what is supposed to happen is that we assume no response is
coming and the disposition of comments could say that
... it doesn't say we can close it though
... so i think myself that it should be fine for anyone to
close at that point
... i assume what we should do is file a bug against decision
policy
rubys: yes
<Zakim> MikeSmith, you wanted to say that (at end of normal agenda) I have a question about who other than the original commenter can move bugs to CLOSED, and when
mjs: i think this might be dealt with - bugs get closed when they timeout
MikeSmith: okay, i'll look - if it is already covered then i won't file a bug - i need to get back to the triage team
rubys: anybody have any other
business?
... i have none and hear no others
rubys: any volunteers?
... hearing no other volunteers, i will volunteer
rubys: if no objections, we will adjourn
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found ScribeNick: adrianba Found Scribe: Adrian Bateman Default Present: Sam, Julian, mjs, adrianba, krisk, +39.535.8.aaaa, [Microsoft], eliot, dpenkler, Radhika_Roy, paulc, Mike, Michael_Cooper Present: Sam Julian mjs adrianba krisk +39.535.8.aaaa [Microsoft] eliot dpenkler Radhika_Roy paulc Mike Michael_Cooper Agenda: http://lists.w3.org/Archives/Public/public-html-wg-announce/2011JanMar/0003.html Found Date: 20 Jan 2011 Guessing minutes URL: http://www.w3.org/2011/01/20-html-wg-minutes.html People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]