Bug 293736 - [Browser] Add Browser.getBrowserVersion()
Summary: [Browser] Add Browser.getBrowserVersion()
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-29 17:02 EDT by Christopher Deckers CLA
Modified: 2019-09-06 16:06 EDT (History)
0 users

See Also:


Attachments
A Javascript based approach. (4.03 KB, text/java)
2009-10-29 17:07 EDT, Christopher Deckers CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Deckers CLA 2009-10-29 17:02:00 EDT
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091016 Firefox/3.5.4 XPCOMViewer/0.9a
Build Identifier: SWT 3.6

In the Browser class, there is:
String getBrowserType();

There should also be:
String getBrowserVersion();

This would greatly help with debugging when something does not work, as well as tweaking certain page injections using both type and version.

Reproducible: Always
Comment 1 Christopher Deckers CLA 2009-10-29 17:07:53 EDT
Created attachment 150877 [details]
A Javascript based approach.

I implemented a Javascript based approach (a conversion of a pure JS version, so some browsers are not applicable in the SWT world).

With this, the method I am asking for would look like this:
String getBrowserVersion() {
  return new JSBrowserDetection(this).browserVersion;
}

Of course, there might be ways to query that info with more accuracy using native browser APIs.

Note that certain browsers have different versions between the browser itself and the engine it uses (like Safari). In this case, the version of the engine is probably more interesting.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:06:37 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.