Closed
Bug 288838
Opened 20 years ago
Closed 19 years ago
Cannot let server decide if script is E4X or not (content type)
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: ian, Unassigned)
References
()
Details
Attachments
(1 file)
|
742 bytes,
text/html
|
Details |
If I have a <script src=""> element that points to an external JS file, I have no way of making the script claim to be using E4X without modifying the calling HTML file. I _should_ be able to just change the script's MIME type to have the e4x=1 flag and then it should just become E4X enabled. TESTCASE: http://www.hixie.ch/tests/adhoc/http/content-type/js/002.html See also related bug 288835 (type="" takes precedence) and bug 100924 (can't use E4X in event handler attributes).
Comment 1•19 years ago
|
||
Derived from the linked URL. This uses data URI's to explicitly show that the data types are indeed text/javascript;e4x=1. Also, there's a halfway step to show that e4x is indeed working when the type is forced in the script tag.
Updated•19 years ago
|
OS: Linux → All
Hardware: PC → All
Summary: Cannot let server decide if script is E4X or not → Cannot let server decide if script is E4X or not (content type)
Comment 2•19 years ago
|
||
Well e4x is already partially enabled even without the e4x=1. Brendan said that
only top-level XML comment and CDATA literals are ignored without e4x=1. So try
this:
if (false)
<!--comment-->
alert('e4x enabled');
| Reporter | ||
Comment 3•19 years ago
|
||
Not how the Web works, it seems.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•