| Summary: | [Browser] new browser support chose wrong default | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Mazen Faraj <mfaraj> |
| Component: | UI | Assignee: | Tim deBoer <deboer> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Mazen Faraj
Tim, consider adding another radio button to the preference page: (*) Internal browser ( ) Default system browser <--- new ( } External browser from the list The second choice would simply mean 'use Program.launch' and pick whatever is system giving you. I suggest we switch to that choice if internal browser is not available, unless we know about some os/ws combinations where the system browser does not exist or is not a good choice. In particular, we should never get in a situation where we have no external browsers in the list and cannot use embedded widget. 'Program.launch' is better than doing nothing. On platforms where there are multiple browsers found, and the default system browser is also detected, we should initially check the browser that matches the default system browser. On my Windows system, out of IE, Mozilla and Netscape 4.7, Netscape is checked by default, which is the last choice I would make :-). I should have been either IE or Mozilla depending on my system default. We can easily find the default by calling 'Program.findProgram (extension)' and call 'Program.getName()' on the return value. The default system browser is now moved to the external browser list to fix some UI concerns. It will always be available and selected by default when this support is available through SWT. |