Loading ...
Sorry, an error occurred while loading the content.

277Re: [caplet] Code that lexes differently in ES3 vs ES3.1

Expand Messages
  • Brendan Eich
    Feb 10, 2009
      No need to apologize, and I did not aim to blame Opera or Safari in citing the record. This was not a situation where anyone fielding a browser compatible enough to get market share could break the de-facto standard that IE set in the wake of Netscape going down (Netscape 4 was based on early SpiderMonkey code, which did not allow / unescaped in a character class).


      On Feb 9, 2009, at 11:31 PM, Marcel Laverdet wrote:

      My apologies.

      On Feb 9, 2009, at 10:54 AM, Brendan Eich wrote:
      No, other browsers followed suit first.

    • Show all 13 messages in this topic