IE11 on Windows 8.1 can cause `tablet` to be true #89

pmilla1606 · 2015-06-10T15:30:53Z

Checking for mobile and tablet can potentially cause false positives on certain Windows 8 devices (in our case a Asus X551M but users reported issues from MS Surface's as well).

We did not catch this using the MS provided VM's.

I realize that this is not technically a bug in bowser but I wanted to put this out there in case anybody else runs into the same issue.

To get around this we are now doing the following:

if ((bowser.tablet || bowser.mobile) && !bowser.msie) { etc }

The text was updated successfully, but these errors were encountered:

serohm · 2015-12-11T21:04:40Z

I have face this issue and to be more specific the false positive is on laptops IE10+ with touch capability.
The user agent in touch devices with IE10+ is:
Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; Touch; rv:11.0) like Gecko

While for non touch laptops (which works fine) is:

Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)

Cheers,

Sergio

mattnorris · 2016-01-25T22:53:50Z

👍

digital-void · 2016-05-17T11:06:56Z

I could verify this - - on a dual monitor no touch desktop pc.
It seems that if you have a Wacom Tablet installed this is true as well - doesn't need to be a touch screen mon - (wacom has touch capabilities as well)

lancedikson · 2016-05-17T13:07:39Z

@digital-void, thanks, and what kind of Wacom Tablet do you use? What about UA in that case? It would be helpful if you send to us browser's UA :)

digital-void · 2016-05-17T14:04:57Z

Wacom Intuos Pro - but I guess this will happen with all touch input devices on windows, as there is no difference between an external or monitor build in touch-input-device on the api side. Same thing happening on my Chintiq Companion - it's no touch screen monitor - but a monitor with a build in stylus system - that is touch capable... And - - - what do you mean with UA?
2 things I want to point out regardless of this issue:
First of: Thank you - for your time and patients!
Secondly:
Could you probably build in a result that is switchable?
Like -

  switch(bowser.agent){
    case ie:
      doSomeIeSpecial();
      break;
    case chrome:
      doSomeChromeSpecial();
      break;
    default:
      doDefault();  
  };

cheers -
patrick

lancedikson · 2016-05-17T14:16:14Z

@digital-void, I meant user agent string, that available as window.navigator.userAgent. Could you paste it from MS IE here, please?

And yeah, I've thought about that case — add something like agent and platform, which would contain the browser name and the platform name. But it's only a think. I'd try to implement it soon.

digital-void · 2016-05-17T14:37:51Z

sure:
Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729; Tablet PC 2.0; GWX:QUALIFIED; rv:11.0) like Gecko
It says Tablet PC 2.0 - but - I promise - it's not ;)
About the switch: I guess this might be really helpful for evron.
It's not urgent but for the sake of completeness ... probably you should ;)
... and thank you again for this neat peace of code... it really helped my out!
I needed a browser switch for unity webplayer on ie, edge and oprea vs. webgl on chrome and firefox (if not webplayer installed ;) )
Maybe something you could state out if people say - "use features..."
Probably a flag x86 - amd64 would be nice....

lancedikson · 2016-05-17T14:44:59Z

@digital-void, interesting. Thank you. I'll test it ASAP and I'm thinking about that feature with additional flags for platform.

digital-void · 2016-05-17T14:51:24Z

Actually - the platform is only a part of it - heaps of people use Firefox 32bit - event though they're on an 64bits os...
I don't know how - but it would be interesting to know how many RAM an application could take.
Another point of interest would be the heap size ... but I'm not sure if this can be determined.
But complex WebGL developments would benefit from that knowledge.
To cut it short:
bowser.ram in byte
bowser.heapsize in byte
would be realy realy something that could give bowser an unique feature ;)
(just thinking)

digital-void · 2016-05-17T14:55:36Z

btw - your support is outer standing ;)

shaibv · 2016-10-25T08:32:25Z

Hi,
Is there any progress with this issue?

lancedikson · 2016-10-25T08:55:51Z

Hi, @shaibv! Actually, not yet. Do you have the same problem? Describe it, please.

shaibv · 2016-10-25T10:35:50Z

Hi,

Yes, I have the same problem.
Touch PC is detected as mobile on a touch device running I.E.

shaibv · 2016-10-25T18:12:09Z

Hi,

Yes, I have the same problem.
Touch pc is detected as mobile on a touch device running I.E.

Thanks,
Shai

On Tue, Oct 25, 2016 at 11:55 AM, Denis Demchenko [email protected]
wrote:

Hi, @shaibv https://github.com/shaibv! Actually, not yet. Do you have
the same problem? Describe it, please.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#89 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AETNShldMH7R_mYOcRZiMSZfiZWfeKUQks5q3cQbgaJpZM4E-jpp
.

lancedikson · 2016-10-25T18:31:40Z

Could you, please, provide your navigator.userAgent string? It could help to fix the problem.

On 25 Oct 2016, at 13:35, shaibv [email protected] wrote:

Hi,

Yes, I have the same problem.
Touch PC is detected as mobile on a touch device running I.E.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #89 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AB3YW2huAFISStk_XO_huHqLIi6wpfpNks5q3duHgaJpZM4E-jpp.

shaibv · 2016-10-26T06:20:54Z

Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; Touch; LCTE; rv:11.0)

shaibv · 2016-11-03T15:19:11Z

Hi @lancedikson
I've talked with my clients and apparently Windows Surface desktop will always be detected as tablet.
User Agent: Mozilla/5.0 (Windows NT 6.3; ARM; Trident/7.0; Touch; rv:11.0) like Gecko

Do you have any idea how can I work around this issue?

related to #89

lancedikson · 2016-11-03T15:41:21Z

@shaibv, I put some tests for the devices that you've prevented above and tests are passed: https://travis-ci.org/ded/bowser/builds/172985408
Do you use the latest bowser version?

shaibv · 2016-11-06T09:22:58Z

Hi @lancedikson ,
I'll try to investigate it further.
Thanks for you'r quick response!

lancedikson · 2016-11-09T11:07:26Z

@shaibv, any news about that? :)

shaibv · 2016-11-09T11:24:41Z

Hi,
I wasn't able to reproduce it using a fake user agent and I don't have
access to the machine.
So I had no choice but to define a machine running IE as not mobile nor
tablet.
Thanks for your support I'll keep following this thread hoping for a more
elegant solution.

On Wed, Nov 9, 2016 at 1:07 PM, Denis Demchenko [email protected]
wrote:

@shaibv https://github.com/shaibv, any news about that? :)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#89 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AETNSuAyH14iwMpdCEU268J64EiyctRkks5q8alwgaJpZM4E-jpp
.

jakedowns · 2016-12-16T21:58:12Z

+1, same here, desktop PC windows 10 with Wacom Cintiq attached.
IE11 v11.576.14393.0

"Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; Tablet PC 2.0; rv:11.0) like Gecko"

bowser.tablet === true

Doesn't happen with MS Edge: "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393"

bowser.tablet is undefined in that case

lancedikson · 2016-12-16T22:21:25Z

@jakedowns, thanks for the report. It's a known case. But, unfortunately, I can't suggest you any workaround for it. Bowser just makes some guesses using UserAgent string and it could be wrong because of those cases, when a tablet attached to PC.

jakedowns · 2016-12-16T22:42:26Z

that's fair. thanks for the prompt feedback and a great utility. been using it for years on all our projects

…

On Dec 16, 2016, at 5:21 PM, Denis Demchenko ***@***.***> wrote: @jakedowns, thanks for the report. It's a known case. But, unfortunately, I can't suggest you any workaround for it. Bowser just makes some guesses using UserAgent string and it could be wrong because of those cases, when a tablet attached to PC. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

lancedikson · 2018-07-09T18:58:26Z

I guess, we can close this for now, since there is no clear solution for it.

lancedikson added a commit that referenced this issue Nov 3, 2016

Add tests for some devices on Windows

c7d663a

related to #89

lancedikson closed this as completed Jul 9, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

IE11 on Windows 8.1 can cause `tablet` to be true #89

IE11 on Windows 8.1 can cause `tablet` to be true #89

pmilla1606 commented Jun 10, 2015

serohm commented Dec 11, 2015

mattnorris commented Jan 25, 2016

digital-void commented May 17, 2016

lancedikson commented May 17, 2016

digital-void commented May 17, 2016

lancedikson commented May 17, 2016

digital-void commented May 17, 2016

lancedikson commented May 17, 2016

digital-void commented May 17, 2016 •

edited

Loading

digital-void commented May 17, 2016

shaibv commented Oct 25, 2016

lancedikson commented Oct 25, 2016

shaibv commented Oct 25, 2016

shaibv commented Oct 25, 2016

lancedikson commented Oct 25, 2016

shaibv commented Oct 26, 2016

shaibv commented Nov 3, 2016

lancedikson commented Nov 3, 2016

shaibv commented Nov 6, 2016

lancedikson commented Nov 9, 2016

shaibv commented Nov 9, 2016

jakedowns commented Dec 16, 2016

lancedikson commented Dec 16, 2016

jakedowns commented Dec 16, 2016 via email

lancedikson commented Jul 9, 2018

IE11 on Windows 8.1 can cause tablet to be true #89

IE11 on Windows 8.1 can cause tablet to be true #89

Comments

pmilla1606 commented Jun 10, 2015

serohm commented Dec 11, 2015

mattnorris commented Jan 25, 2016

digital-void commented May 17, 2016

lancedikson commented May 17, 2016

digital-void commented May 17, 2016

lancedikson commented May 17, 2016

digital-void commented May 17, 2016

lancedikson commented May 17, 2016

digital-void commented May 17, 2016 • edited Loading

digital-void commented May 17, 2016

shaibv commented Oct 25, 2016

lancedikson commented Oct 25, 2016

shaibv commented Oct 25, 2016

shaibv commented Oct 25, 2016

lancedikson commented Oct 25, 2016

shaibv commented Oct 26, 2016

shaibv commented Nov 3, 2016

lancedikson commented Nov 3, 2016

shaibv commented Nov 6, 2016

lancedikson commented Nov 9, 2016

shaibv commented Nov 9, 2016

jakedowns commented Dec 16, 2016

lancedikson commented Dec 16, 2016

jakedowns commented Dec 16, 2016 via email

lancedikson commented Jul 9, 2018

IE11 on Windows 8.1 can cause `tablet` to be true #89

IE11 on Windows 8.1 can cause `tablet` to be true #89

digital-void commented May 17, 2016 •

edited

Loading