Databases
StackOverflow2013
Postsdbo
PODetecting browser versions on recent mobile devices
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODetecting browser versions on recent mobile devices
    primarykey
    data
    text
    <p>I have a need to differentiate between the native (Android) browser and Google Chrome on more recent Android devices, but keep running into problems, specifically with more recent Samsung devices (the Galaxy S4, Galaxy S4 mini and Galaxy Mega).</p> <p>We have some device detection in-house which analyses the user agent sent from the browser to try and determine which browser is being used. Traditionally to detect Chrome, the code would look for either "Chrome" or "CriOS" within the user agent, normally these are present in the last part of the user agent string (according to the <a href="http://en.wikipedia.org/wiki/User_agent" rel="nofollow noreferrer">Wikipedia article</a> on User agents, this is used to indicate available enhancements).</p> <p>Up until very recently, this worked without issue*.</p> <p>On the latest Samsung Galaxy devices (listed above) running Android 4.2.2, the native browser returns "Chrome" in the user agent string. From some brief reading around the subject, this is because the native browser uses Chromium (I'll admit, I didn't understand the differences between Chromium and Chrome until I read around the subject a bit, more info <a href="http://en.wikipedia.org/wiki/Chromium_%28web_browser%29" rel="nofollow noreferrer">here</a>).</p> <p>This also invalidates the use of Chrome feature detection suggested <a href="https://stackoverflow.com/a/13348618/572585">here</a>.</p> <p>The main issue with this is that we're seeing minor rendering differences between the two browsers, which we'd normally handle with browser specific CSS hacks**, which we're now unable to use.</p> <p>So far, we've only seen this issue on Samsung Galaxy devices, when tested on a Nexus 4 running Android 4.2.2, the native browser does not return Chrome as part of the user agent. It could be that this is a problem very specific to Samsung Galaxy devices running Android 4.2.2, but at this juncture, we don't have a broad enough range of devices to test on.</p> <p>Does anyone know of any way of reliably differentiating between the two browsers without using either of the two methods above?</p> <hr> <p>*that's without any issues that we've noticed or that have been reported to us.</p> <p>**yes, I know using hacks isn't the best way of doing things, but when it's that or re-write large chunks of the code, hacks tend to win out.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USDark Hippo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PODetecting browser versions on recent mobile devices
      1. USLior Cohen
      1. VTFavorite
    1. COYou might also consider asking specific questions about the layout problems to see whether you can do without browser sniffing.
      singulars
      1. PODetecting browser versions on recent mobile devices
      1. USPointy
    2. COWe could, but 1) a solution would be nice just in case any other browser specific issues arise (we've already has some which we've managed to find hacky ways around, and 2) the main small layout issue can be fixed by removing a single CSS property, which fixes it on Safari and Chrome, but breaks it on native, hence a browser specific fix. We don't control the majority of the CSS for this particular feature, we're using overrides to modify the layout provided to us, so the less CSS work needed, the better.
      singulars
      1. PODetecting browser versions on recent mobile devices
      1. USDark Hippo
    3. COOh I understand of course; just a suggestion.
      singulars
      1. PODetecting browser versions on recent mobile devices
      1. USPointy
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload