- From: Brian Birtles <bbirtles@mozilla.com>
- Date: Thu, 06 Jun 2013 15:56:42 +0900
- To: www-svg@w3.org
(2013/06/04 18:20), Cameron McCormack wrote: > krit: what about using the text area element from 1.2? > > heycam: the name is bad > > shepazu: in 1.2 we define an algorithm and I don't think that's > a good idea for what I'm proposing > ... I just want to make it super easy to use and intuitive and > rely on the behaviour that comes out of CSS > > krit: the switch of behaviour of the text element with > exclusion or width and height is confusing to me > ... for shapes suddenly x and y are not relevant anymore > ... and for your propsal y changes meaning Sorry, I guess I wasn't following the conversation properly at this point but I just want to second Dirk's point here. I find the idea that x/y change meaning depending on the presence of the width attribute surprising. I can certainly imagine authors cursing SVG at the top of their lungs when their carefully positioned textbox suddenly shifts up because they removed a width attribute (which may not have even been having a noticeable effect depending on its value). (And I can likewise imagine WONTFIXing the corresponding bugs they file on UAs when they finally discover the link between the vertical jump and the presence/absence of the width attribute.) But perhaps I have misunderstood the proposal? If not, is it too late to consider <textbox>, <textrect> or some other name? Best regards, Brian
Received on Thursday, 6 June 2013 06:57:09 UTC