Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Element#update
now takes care of SCRIPT elements in IE. [#573 state…
…:resolved]
- Loading branch information
Juriy Zaytsev
committed
Mar 22, 2009
1 parent
2c986d8
commit 71a8663
Showing
3 changed files
with
33 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
71a8663
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is missing a test to verify
Element#update
correctly evaluates the content it is passed.71a8663
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m a bit uneasy about this feature test. We’re interested in making sure that the content attached to a script element is evaluated. Here we’re testing that it’s doesn’t throw an error. That’s very different, imho.
71a8663
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had the same concerns and actually first made a test which ensures content evaluation. The problem was Safari 2, which required `document.write` and `document.write` completely destroys our unit test runner. Any ideas on what we can do about it?
71a8663
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should target Safari 2.0.4 (that is, fully patched version of 2.0) which solves this problem altogether.
71a8663
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds reasonable. AIUI, this will also make it possible to implement “global eval”