- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Tue, 22 Mar 2011 19:07:42 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: "www-style@w3.org" <www-style@w3.org>
On 03/22/2011 06:46 PM, fantasai wrote: > On 03/22/2011 04:13 PM, Tab Atkins Jr. wrote: >> >> I prefer the Chrome/IE behavior, given that we're calculating the size >> of an inline replaced element. I wouldn't want it to act like a block >> by default and get all huge, automatically dropping down to the next >> line of text. Keep in mind also that the sizing rules here apply to replaced blocks as well as replaced inlines. > The resolution was to make it undefined because, due to the misinterpretation > of SVG's percentage widths and heights as intrinsic widths and heights, we > have no implementations. It does not override the previous resolutions we had > that this is the correct and desired behavior. > > 300x150 is useless for SVG. If you want it, you can get it by specifying > explicitly. But if you want to insert a pretty picture or a graph, the > behavior currently in the spec is much more useful, and not something you > can get otherwise.
Received on Wednesday, 23 March 2011 02:08:17 UTC