Chrome browser (version 23.0.1271.97) on Windows 8 desktop is erroneously recognized as supporting touch events. Actually it is a desktop, that is to say, it doesn't support touch events.
See for example Modernizr Touch tests: http://modernizr.github.com/Modernizr/touch.html
Did anybody run into this problem?
Is there a solution or a workaround?
Related
I'm making my portfolio website and I'm using pure HTML 5 no .js the about page doesn't work on iPhone and doesn't scroll everything together some of the elements positions are fixed and don't scroll. I don't own an iPhone but is there anyway to simulate the iOS on computer so I can debug the page? And is there such a tool like "inspect element" in chrome on the iOS safari? If not how can I debug and find how the browser is rendering wrong on the phone? Cause I validated my code and it's supposed to work, but its not!
You can simulate iOS using Xcode and Mac OS.
And for the debug purpose there is no inspect element in Simulator. Yes you can take a help of Accessibility Inspector
In the Simulator >> Go to Settings >> General >> Accessibility
Turn on Accessibility Inspector - This will help you to inspect different elements.
Something important to bear in mind is that because of Apple's policies, all browsers must use Safari’s layout engine to render pages, that means there are very few differences in rendering a page between Safari and other browsers on iOS.
There are two methods that you can use to debug a web page running on your iOS device on your using a browser on your Mac or Windows computer:
1. Debug using a Mac
If you have a Mac, you already have tools to live-inspect and debug web pages on your iOS device.
See here: https://developer.apple.com/library/safari/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/Introduction/Introduction.html
2. Debug using Windows
Xcode and MacOS are not the only way to debug websites running in a browser on OSX. There's a few ways:
Telerik
WineRE
I personally use Edge Inspect when I'm forced to use Windows.
Adobe Edge Inspect
http://www.adobe.com/devnet/edge-inspect/articles/browser-testing-across-devices-with-adobe-edge-inspect.html
I am working on a mobile website at the moment and I refreshed the page, Chrome quit unexpectedly, and since then all touch screen emulation is absent and/or failing.
Chrome Version: 36.0.1985.125 m,
OS: Windows 7 Ultimate SP1
Google Chrome suddenly and unexpectedly stopped emulating devices properly. All touch screen functionality has been disabled and apparently removed. When I emulate a device, the Sensors box fails to be checked and upon inspection, does not show any 'Emulate Touch Screen' option.
I have tried the following, all in conjunction:
Uninstalling/Reinstalling Chrome and deleting all personal settings, including uninstalling all extensions, restoring all defaults, etc.
Restarting the computer
Running anti-virus software
EDIT: Installed Chrome Canary which produced the exact same problem
Please let me know if there are any other relevant details that I might need to add.
Sorry about this. We overhauled the touch emulation in Chrome 36 to be much more accurate (sharing code with what really happens in Chrome Android): https://plus.sandbox.google.com/+RickByers/posts/CBCmhVttj5C. In the process we ended up disabling touch emulation when real touch support was present (at the time we thought this was no big deal because if you've got a real touchscreen why would you want to fake one with mouse?). But some Windows PCs report that they have a touchscreen when in fact they don't really (Eg. Visual Studio installs a touch screen emulator I believe).
We're fixing this at http://crbug.com/395531 - hopefully there will be a Chrome Canary build soon that re-enables touch emulation in these cases.
In the meantime you can mostly work around the issue by disabling Chrome's support for built-in touchscreens at chrome://flags/#touch-events. Make sure you set this back to 'Enabled' after Chrome is updated to fix the issue. With this disabled, some minor aspects of touch emulation (eg. DOM0 ontouchstart= handlers) will not work properly.
Stop the "Tablet PC Input Service" and restart chrome. If chrome thinks you have a touch screen, it won't let you emulate one.
I stumbled across the answer here:
https://github.com/Modernizr/Modernizr/issues/880
I've been trying to make an audio tag work in as many different browser/OS combinations as possible. Here's the simple snippet of code I am using:
<div class="audioPlayer"><audio src="http://2ndbc.org/podcasts/2013.09.29.m4a" controls=""></audio>
<p>Download this podcast.</p></div>
This works great in Internet Explorer 9 on Windows 7, Safari 6.x on OS X 10.8 and Chrome on OS X. I'm also told it works fine on the latest Chrome and Firefox on Windows 7. However, it doesn't seem to work with Firefox or Chrome on Windows XP. I don't have access to an Android phone, but I was also told by one person that it didn't work on Android. I've tried both M4A/AAC and MP3 files. (As far as I can tell, it should work now that Firefox can support MP3 files.)
I'm hoping I can come up with a solution that lets me avoid using a Flash-based player -- just to keep things simple, yet compatible with any current version browser.
I'm debugging a application that runs great on IE10 desktop version on a windows 8 tablet, but when I'm opening the same app in the metro version of IE10, tapping on buttons in the interfaces doesn't seem to work. This has something to do with how IE10 handles the taps on the screen.
Is there a clear and complete list of differences between IE10 in metro mode and IE10 in desktop mode on a touch enabled screen? If yes, what are those differences?
I cannot make an instance of Worker on Mobile Safari on an iPad with OS 4.2x
This is a very common and well-known HTML5 Web Worker demo: http://html5demos.com/worker
When I try to run I get the error ReferenceError: Can't find variable: Worker
This demo works fine on desktop Safari. My understanding was that with OS 4.2x that HTML5 Web Workers would be supported on mobile safari. Does anyone know different?
At the moment WebWorkers are against Apple's policy on JavaScript runtimes. Even if it were supported it would be thrown out after 10 seconds as the maximum, non-blocking runtime.
According to caniuse.com, it's not yet supported