Community
Participate
Working Groups
The Browser widget has been mostly tested on HTML rendered in memory and HTML documents accessed from local drives (file:/// protocol). A next step would be to provide more support and control for content loaded over HTTP. This PR is to investigate how to do this in a portable manner across the supported native browsers. Implementation of new features should not break support for future native browser versions - e.g. not rely on unfrozen API. This will be a work in progress with possibly more items resolved when newer versions of e.g. Safari webkit, Mozilla, IE are released with more embedding API support. At the moment we are looking at compatibility with at least Safari Webkit 1.0, frozen Mozilla 1.4 API and above, IE 5 and above. Code contribution to the items below that match the compatibility criteriae is very welcome (please open separate bug report) Areas to be investigated: 1. Profile settings a. HTTPS support on Mozilla - bug 83016 (require profile support) b. HTTP accept-language - bug 77456 bug 77371 and support for other non Mozilla platforms c. set a cookie d. set other user preferences 2. File Download event notification with possibility to cancel
Also related to: 1. Profile settings 1.d set HTTP Proxy settings bug 82295
Fix a typo in bug for HTTPS. New list is: Areas to be investigated: 1. Profile settings a. HTTPS support on Mozilla - bug 83033 (require profile support) b. HTTP accept-language - bug 77456 bug 77371 and support for other non Mozilla platforms c. set a cookie d set HTTP Proxy settings bug 82295 e. set other user preferences 2. File Download event notification with possibility to cancel
Fix yet another typo in bug for HTTPS. New list is: Areas to be investigated: 1. Profile settings a. HTTPS support on Mozilla - bug 80033 (require profile support) b. HTTP accept-language - bug 77456 bug 77371 and support for other non Mozilla platforms c. set a cookie d set HTTP Proxy settings bug 82295 e. set other user preferences 2. File Download event notification with possibility to cancel
- #1a, #1b and #1d have been addressed since this report was logged - reports exist for the other listed items: -> #1c is logged as bug 187315 -> #1e should be handled on a per-setting basis -> #2 is logged as bug 83444 (example: http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet277.java?view=co ) Additionally, all of these can now be accomplished with an SWT.MOZILLA Browser via JavaXPCOM. Marking report as a duplicate of 1c. *** This bug has been marked as a duplicate of bug 187315 ***
To extend 1c, you'd also need support to get cookie.
