Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332416 - [Intro] When introPage is "content" javascript cannot be executed if the script contains '<', '>' or '&'
Summary: [Intro] When introPage is "content" javascript cannot be executed if the scri...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-ua-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-13 04:38 EST by Mickael Istria CLA
Modified: 2019-11-14 03:40 EST (History)
1 user (show)

See Also:


Attachments
Some XHTML intro pages that shows some failing JS scripts when loaded as "content" in "introContent.xml" (2.24 KB, application/x-zip)
2010-12-13 04:38 EST, Mickael Istria CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mickael Istria CLA 2010-12-13 04:38:01 EST
Created attachment 185042 [details]
Some XHTML intro pages that shows some failing JS scripts when loaded as "content" in "introContent.xml"

Link the product with an introContent.xml, and load an xhtml page using "content" attribute (not "url").
Whenever the script contains an '<', '>' or '&' character, either in an inlined script in the html document, or in a referenced script in an external JS file, there is no way to get it working.
I tried escaping characters to their HTML replacement, using CDATA, externalizing script, and I think all combinations of the 3, but couldn't get such scripts working.

See attachement for examples.
Comment 1 Mickael Istria CLA 2010-12-28 10:13:32 EST
I just try to create an IIntroXHTMLContentProvider to inject the JavaScript into the page, but it has the same limitations that by directly writing JavaScript in the page.
There is currently no workaroud.
Comment 2 Christian Schneider CLA 2011-08-31 08:45:50 EDT
it works fine over here (indigo on win64) if you put a 
//<![CDATA[
at the beginning
and 
//]]>
at the end of the javascript.

Seems it just has to be valid xml overall. So this bug is invalid.
Comment 3 Lars Vogel CLA 2019-11-14 03:40:56 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.