- From: <bugzilla@jessica.w3.org>
- Date: Wed, 13 Apr 2011 21:52:42 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11239 --- Comment #13 from Charles Pritchard <chuck@jumis.com> 2011-04-13 21:52:40 UTC --- (In reply to comment #12) > Working Group Decision: In relation to this decision: * The change to add baseline to the TextMetric interface is not adopted. "... noted the editor's question 'which baseline?'" Naseline properties are defined by the textBaseline section of the existing specification. When an author sets textBaseline to a value, that is the baseline which would be used for the TextMetric.baseline property. Such information is easily accessible to implementers, see for example, drawTextInternal http://trac.webkit.org/browser/trunk/Source/WebCore/html/canvas/CanvasRenderingContext2D.cpp The value is calculated from a combination of the ascent, descent and font height metrics. In relation to this decision: * The change to remove the canDrawCustom parameter from drawFocusRing is not adopted. It's my understanding that such a parameter would be specified via CSS, such as the css outline property, as is done on other HTML elements when they are focused. As in HTML, authors are not guaranteed that the UA/AT will "skip" drawing focus indicators. canDrawCustom seems only to duplicate the already existing semantics CSS provides. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Wednesday, 13 April 2011 21:52:43 UTC