Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 268519

Summary:	non API use in visualization process
Product:	z_Archived	Reporter:	Kentarou Fukuda <kentarou>
Component:	ACTF	Assignee:	Kentarou Fukuda <kentarou>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Kentarou Fukuda

2009-03-13 07:53:45 EDT

To visualize or evaluate accessibility of Web content, we need to obtain HTML source, live DOM, etc. from Browser component. We use our own browser for this purpose, but other projects uses SWT browser (SWT browser Editor (WebTools) or browser output view (PDT)) to preview Web content.

In current implementation, when users select accessibility visualization action, we reopen the Web content into ACTF Web browser and visualize/evaluate accessibility. However, there are no APIs to get target URL from SWT browser editor or target HTML text from browser output view. So, we currently use reflection method to get these information.


Migration plan:

Short term:
1. Ask SWT team to enable to get current URL from SWT browser editor.
 via API, store the URL into IEditorInput, etc. 

2. Ask PDT team to enable to get target HTML as text from browser output view.

(3. or add preference page, etc. to enable users to select preview browser.)

Long term:
Investigate difference between our browser and SWT browser and create migration plan. 
 -If we can transfer our required functions into SWT browser itself, it might be the best.
 -If we can implement our required functions as wrapper/extension of SWT browser, it might be a good solution.

Comment 1 Kentarou Fukuda

2017-06-11 12:02:46 EDT

I submitted new bug about WebBrowserEditor for Eclipse Platform UI team (Bug 518100).

Currently, PDT also uses WebBrowserEditor. So, if we can solve the issue on WebBrowserEditor, we do not have to any additional update for PDT.