<div dir="ltr"><br><br><div class="gmail_quote">On Wed, Oct 15, 2008 at 8:22 AM, Eduard Pascual <span dir="ltr"><<a href="mailto:herenvardo@gmail.com">herenvardo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, Oct 15, 2008 at 10:40 AM, Ian Hickson <ian@hixie.ch> wrote:<br></div></blockquote><div><snip> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
</div><div class="Ih2E3d">> I am very reluctant to make up a whole<br>
> new microsyntax and corresponding parser algorithm, along with all the<br>
> tests, etc, to handle this one case.<br>
<br>
</div>I still don't understand why the spec has to define each and every<br>
parser algorythm (IMO, it should only define the syntax, and then the<br>
implementation should define its own algorythm that parses that syntax<br>
as defined); but if that's the issue then a microsyntax can be<br>
perfectly avoided by splitting the argument into two separate ones,<br>
such as pixelratiox and pixelratioy.</blockquote><div><br>The only issue I have with splitting it into separate ones, is that we need to<br>ensure that both exist or none exist, having just X or just Y is clearly confusing<br>
and should not be allowed.<br><br>-- Sander<br><br></div></div><br>
</div>