See also: IRC log
<trackbot> Date: 12 January 2012
<scribe> scribe: janina
Discussion of whether to create a new tag to indicate the TF has worked on, and finished work, a particular bug.
Suggestion to create a TF tag to indicate need to revisit
Agreement to postpone to next week as it doesn't help us meed this week's deadline.
Bug Subteam will meet again Friday at 1PM Boston
<paulc> What is the keyword for HTML.Next?
Janina: Suggest focus only on what needs Friday escalation
Rich: This affects more than
... Will work on this in Indie UI
Agreement to assign to Web API guide
Paul: WG isn't getting the notice
when this is moved to another WG. People have complained when
the editor has done this.
... Suggests creating a new bug to achieve this, not move an existing bug
... Same problem if component move, e.g. from LC to API component
CS: Issue q: ARIA disallows changing role
js: Global issue is dynamic changes are a major a11y concern. There's needs to be the appropriate place to manage that globally
ms: Confirms that bugs are not dropped, ever.
cs: Shouldn't escalate without examples
JS: Asks level of confidence that Bug Triage can finish Friday?
mc: 40 bugs needs info, have
identified 5 categories
... Expectation to finish re escalation
mc: Triage will make sure there's a tracker for canvas issues
cs: Probably need separate canvas trackers, as some of the issues aren't related
mc: if they're obviously different
rs: 131 anything to do with carat
focus ring selection
... text base line we have cp, but no tracker
... need tracker for path to element
cs: i did them a bit differently
... anything to do with text editing in canvas, ie will not support
rs: nothing to do on subdom
because part of spec already
... think resolving scroll path into view will be sufficient
<MichaelC> Canvas bugs: 9061, 11240, 12306, 12906, 14419
<David> Cynthia, can you drop those 4 categories into the Chat here?
<paulc_> Current non-processed TrackerRequest's: https://www.w3.org/Bugs/Public/buglist.cgi?product=HTML%20WG&keywords=TrackerRequest
rs: We need issue relating to providing bounds of an element which also allows hit testing
cs: position and hit testing in
the same issue is OK
... want text separated out
pc: question on ball park estimate of additional requests?
mc: expects as many as 5 issues
pc: are you thinking a tracker on a single bug then relate the others?
mc: would like input on that
pc: suggest bugs a, b c, d all relate to e, and put tracker on e
jb: text met tuesday, started
planning for when longdesc came up, talked about alt guidance
concerns, title and meta generator pending
... also processed 10 text related bugs
... asking when longdesc might come out?
pc: still processing one of the cp's, so no further data yet
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: janina Inferring ScribeNick: janina Default Present: John_Foliot, Judy, Michael_Cooper, paulc, Cynthia_Shelly, Janina_Sajka, Rich, David_MacDonald, Mike Present: John_Foliot Judy Michael_Cooper paulc Cynthia_Shelly Janina_Sajka Rich David_MacDonald Mike Regrets: Léonie_Watson Laura_Carlson WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 12 Jan 2012 Guessing minutes URL: http://www.w3.org/2012/01/12-html-a11y-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]