On 5/18/07, Thomas Fuchs [EMAIL PROTECTED] wrote:
This has been addressed with changeset 6752.
What about these closing tags:
http://dev.rubyonrails.org/browser/spinoffs/prototype/trunk/src/dom.js#L860
Crockford says there should be no sequences of / left unescaped.
This has been addressed with changeset 6752.
best,
thomas
Am 15.05.2007 um 02:13 schrieb W. Niu:
I support making it inline-compatible if all it takes is a couple of
backslashes. However, we strongly advise W. Niu to change his CMS.
To be honest, I am not fond of that approach either,
As a reference, the same fix that Christophe presented is shown near
the top of this page: http://javascript.crockford.com/script.html
The quote from the page reads: The script should not contain the
sequence / because it could be confused with the /script. Inserting
a backslash between and /
On 5/14/07, Ryan Schuft [EMAIL PROTECTED] wrote:
Out of curiosity, why would the fix not go into the main distribution?
Embedding a 90+ KB (which is Prototype) in a document is insane. This
applies to online web pages, while for offline content it could make sense
in a scenario when you want
Hello there,
W. Niu a écrit :
I'd just like to report a small issue I encountered when trying to
upgrade from 1.5.0 to 1.5.1. I suspect this is more likely to be an
issue from Firefox (2.0.0.3) script parser though.
Actually it's no issue, it's entirely nominal. HTML mandates that an
