- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Tue, 12 Jun 2018 10:26:52 +0200
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: ddailey <ddailey@zoominternet.net>, "Amelia Bellamy-Royds" <amelia.bellamy.royds@gmail.com>, www-svg <www-svg@w3.org>
On Mon, 11 Jun 2018 18:32:47 +0200, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Sun, Jun 10, 2018 at 3:30 AM Steven Pemberton > <steven.pemberton@cwi.nl> wrote: >> But it's a restriction, not a feature. You don't support a restriction, >> but adhere to it. By lifting the restriction you don't introduce any >> incompatibilities: old SVG files still render properly; however, by >> lifting it you do add new possibilities, and make life easier for SVG >> authors. > > Not always the case. There may be SVG files in the wild which are > currently using this syntax and (accidentally) *relying* on it being > invalid, so that making it valid would suddenly mess up the image. > (This isn't uncommon in CSS.) But it's an *error*. "The document shall be rendered up to, but not including, the first element which has an error. " Are you telling me that people are depending on rendering to stop because they have used a negative height on a rectangle? Seems very unlikely to me. Best wishes, Steven Pemberton
Received on Tuesday, 12 June 2018 08:27:31 UTC