This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#dom-context-2d-textbaseline-middle Comment: Why does the definition of "middle" differ from the one in SVG 1.1 10.9.2? Posted from: 212.61.239.181
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Because the SVG definition, and more importantly the CSS definition on which the SVG one is based, is esoteric and isn't what people think of when they think of 'middle'. What do browsers implement? If browsers use the same definition for 'middle' here as for CSS and SVG, we can change it. (It looks like Opera does 'middle' per CSS/SVG, and Gecko/WebKit do it per the HTML spec. Haven't figured out how to test IE9 yet.)
boogyman helped out. IE9 also does it per spec. So I think it's probably too late to change.
mass-move component to LC1