If engines pass parsing through to system libraries, it may be difficult
for them to fully specify their quirks.
Having things that currently fail become valid could also change the
behaviour of existing programs that do speculative parsing; something to
keep in mind.
On Thu, Jun 9, 2016 at 12:42 AM, Morgan Reece wrote:
> I'm trying to create a union of the quirks, though it may indeed turn out
> to be an intersection instead. If that is the case my hope is that other
> implementations will compromise by submitting amendments to the proposal.
> 2016-06-09 0:33 GMT-07:00 :
> > On Wednesday, June 8, 2016 at 2:29:03 PM UTC-7, Morgan Reece wrote:
> > > After spending some time looking at the date parsers in SpiderMonkey,
> > > and Chakra I think the most sensible way to fix this situation once and
> > for
> > > all is to create a date parsing grammar and lobby to have it put into
> > > spec. I've been fiddling around with a working implementation for the
> > past
> > > few days and would appreciate any feedback or improvements.
> > Morgan, are you trying to create a grammar that strictly matches the
> > EMCA-262 spec or one that matches the (union or intersection of) quirks
> > heuristics used in different browsers?
> > chris
> > _______________________________________________
> > dev-tech-js-engine-internals mailing list
> > email@example.com
> > https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
> dev-tech-js-engine-internals mailing list