Bug 255749 - [Browser] Loading XML in SWT Browser via setText()
Summary: [Browser] Loading XML in SWT Browser via setText()
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 123748 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-11-19 00:51 EST by Timothy Fridey CLA
Modified: 2019-09-06 16:09 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Fridey CLA 2008-11-19 00:51:14 EST 
Currently if you use the setText(String s) method to send xml data to the browser in the form of a string. It is always recognised as HTML, the url is passed to IE as about:blank.
An option to define if the content is xml or html would be great currently I must save my xml to a file and open via the url.
Simply adding .xml to about:blank may be enough to trick IE to thinking it is opening an XML file.
Comment 1 Mike Wilson CLA 2009-05-05 12:20:27 EDT 
Changing Version tag to something more believable. Note that this is not a statement about when the enhancement request will be addressed (the Target Milestone field is used for that); the Version tag should be set to the version of Eclipse you were using when you saw the need for the enhancement.
Comment 2 Grant Gayed CLA 2010-04-07 15:58:38 EDT 
*** Bug 123748 has been marked as a duplicate of this bug. ***
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:24 EDT 
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.