kangax wrote: > On Mar 21, 7:08 am, "T.J. Crowder" <t...@crowdersoftware.com> wrote: > [...] > > Once we have a solid list, I'll update the page; and then update it > > again if the list changes in 1.6.0.4, as I expect it will (e.g., +IE8 > > at least, perhaps Chrome?). > > I think we pass most of the tests in Chrome. > Chrome is actually doing something very retarded: > > '' instanceof String; // false > ''.constructor === String; // false > ''.escapeHTML === String.prototype.escapeHTML; // false > > This makes some of the string tests fail, since Chrome's native > `escapeHTML` is being used instead of Prototype's > `String.prototype.escapeHTML` (which is effectively ignored)
It's funny how Chrome shows one thing in javascript console and another one when executing from address bar. Sigh. In console, `''.escapeHTML` resolves to Chrome's native `escapeHTML`. Anywhere else - to Prototype's `escapeHTML`. Prototype's escapeHTML uses `innerHTML` escape mechanism (when available). In Chrome, innerHTML would properly escape "<" and "&" but not ">" (no idea why). Making a test more strict solved the issue [1]. [1] http://github.com/sstephenson/prototype/commit/fa15f212fa4bfad5ff4210bafee2913e66cf4758 -- kangax --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
