[Bug 11705] Why does the definition of "middle" differ from the one in SVG 1.1 10.9.2?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11705

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-08 01:35:12 UTC ---
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.)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 8 February 2011 01:35:14 UTC