Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

!noexec option for scripts loaded by js! seems non-functional #17

Closed
unscriptable opened this issue Sep 4, 2011 · 1 comment
Closed
Assignees
Milestone

Comments

@unscriptable
Copy link
Member

The test for the !noexec option for the js! plugin seems broken.

@ghost ghost assigned unscriptable Sep 4, 2011
@unscriptable
Copy link
Member Author

!noexec option removed. The "text/cache" trick no longer works for this purpose. "text/cache" still works for prefetching in browsers that don't yet support async="false", though. It's just that all browsers that support async="false" seem to ignore script elements with unsupported script types (which is the same ting to do).

This feature could be implemented by using doc.createElement('object').onload if demand for !noexec emerges. (doc.createElement('image').onload causes the "sticky mime type" bug in Chrome, so it's not an option atm.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant