after multiple search, I can not find the answer, so I appeal to your knowledge. Since the last Chrome update on android, I can not use my gyroscope on virtual tours online anymore. My gyro includes my up and down motion but not right and left. Firefox is ok... Do you have more information?
Thx
It's a Chrome bug introduced in v65, as it appears from here bugs.chromium.org/. I'm using Chrome Beta to keep testing my work that uses the DeviceOrientation API since it works there. This also means that the bug will be fixed once the stable Chrome reaches v66 publicly.
I have a Windows Phone (a Nokia Lumia) from which I recently encountered an issue. I can't zoom (pinch zoom) or navigate (scrolling with the finger) using Google Maps. It was possible I believe last week or the week before that, but now it's not working anymore.
I can't recall any updates issued in between last working date and now, nor have I fiddled with any options.
I saw in a thread that one could use the options in the browser in order to enable zooming. But this option is not present for me. I use Internet Explorer.
Based from this thread, if it was determined that you are on a desktop version or IE, it will allow zooming to be controlled by mouse. Touch won't work at all. I also found this blog which states that:
The mobile Web version of Google Maps is optimized for WebKit browsers such as Chrome and Safari. However, since Internet Explorer is not a WebKit browser, Windows Phone devices are not able to access Google Maps for the mobile Web.
The desktop version of Google Maps works just fine in these browsers. It's one thing for Google to say the mobile site isn't tested or supported in the mobile browsers, but the desktop version, at least, shouldn't be off-limits. The desktop version may not be ideal in a mobile browser, but it does work.
I'm implementing a web application that uses html5 features.
Is still on localhost. Is there any online service that I can test my localhost site somehow?
I mean, is there an online service that simulates mobile browsers, or versions of older web browsers?
So I don't have to download/install older browsers?
You can use a browser named Lunascape, because its giving you facility to run your site (local and live both) on different 3 rendering engine in same single browser.
And we know that almost all browser uses one of these three rendering engine.
Trident = for IE,Internet Explorer Mobile version and others
Gecko = Firefox, Firefox for mobile and many others
Webkit = Safari, chrome... know more
so you can just switch to any one of these three rendering engine by click on icon at right side of address bar of lunascape browser.
Download and check it. May be it useful to you...Lunascape
Click here for More information about Lunascape
In other option, Avant browser is also good choise. but I like Lunascape more compare to avant, but that is my personal opinion may be you have different experience with one of these two.
Because Adobe Browser lab is shutdown you can also go with BrowserStack or Saucelab but these are paid.
I would use a firefox or chrome plugin (https://chrome.google.com/webstore/detail/test-ie/eldlkpeoddgbmpjlnpfblfpgodnojfjl):
here are a list of services and plugins:
http://www.hongkiat.com/blog/complete-guide-to-cross-browser-compatibility-check/
Install Test IE plugin to Firefox and then run your local site and click to Test IE icon on the right-top of Firefox and choose which version of IE you want.
Note:It has 30 minutes free trial time.
I had the same question today and a coworker told me about BrowserStack. Create a free online account and then install the chrome extension. Fairly easy setup -> Just make sure to click Yes when they ask if you want to do local testing, and it'll guide you through getting started.
The testing options are extremely detailed: I'm using it to check between a Chrome on Mac vs Chrome on Windows styling bug, and it's working perfectly for testing my localhost dev version.
I'm making a website using HTML5 and CSS3 and thinking to use Google Chrome Frame for IE8 and lower because I don't want to for graceful degradation or giving alternative visuals using Modernizer for IE8 and lower. But want to know Is there any performance and any other technical issue with Google chrome Frame?
If Google chrome frame has issue then I will go for graceful degradation or giving alternative visuals using Modernizer.
Google Chrome frame website says
Start using open web technologies—such as the HTML5 canvas tag—right away, even technologies that aren't yet supported in
Internet Explorer 6, 7, 8, or 9.
Take advantage of JavaScript performance improvements to make your apps faster and more responsive.
I want to know comments from any experienced who have use chrome frame.
I think you get it other way around: you as a user can install Google Chrome Frame to use new features, but web site normally is not able to rely on the fact that the Frame is present on user's machine.
Users with older browsers liklely will not be able or willing to install the required plugin.
Is anyone writing applications specifically to take advantage of google chrome?
Are there any enterprise users who are considering using it as the standard browser?
Yes, I have started to pay very good attention to Google Chrome for my applications. Recent analytics show that between 6%-15% of my users are accessing my applications (varies between 6 to 15 in different applications) on Chrome. And, this number looks on an upward trend.
Thus, I can't really ignore it for testing right now.
As far as taking it as a standard goes, thats a long way off. I still have to test for IE6! :( Though, we have been planning to start using features like Gears (inbuilt in Chrome - downloadable elsewhere) once Chrome crosses the 25% mark. Thats when I believe that we will be looking at Chrome to be our preferred browser. I hope that we have Chrome 1.0+ by then! ;)
I switched to Chrome and haven't looked back except for the occasional site which doesn't work properly, forcing me to load it in Firefox. All my existing web applications work fine on it, and I'm using it for primary testing on my current development project.
I'm not actually targeting chrome, but I have added chrome to my browsers to test sites on. I've found some odd quirks in this product where some plugins cause the browser to hang, or run really slow in some environments, but they are still in beta in active development. But I definately now make sure sites I work on render well in chrome, as well as firefox, latest versions of IE, safari, Konquerer and opera. I usually check out how it looks on lynx as well, that helps me catch "un-alternated text" in images. Yeah, I know that isn't a word, but some people will understand what I'm saying.
Because chrome uses the webkit to render HTML, you can be assured if it works in safari, it'll work under chrome, however it's rendering engine isn't up to scratch quite yet. I think writing applications that take advantage of it is similar to writing iPhone applications, remember chrome is expected to be adopted by android to make it similar to iPhone. That way it pretty much takes advantage of all those iPhone apps.
Would I install it as the browser of choice? not yet - but i'll certainly work on valid web pages that will render across all browsers.
One of our major customers has outlawed Chrome because it installs on the C drive without asking. They deploy a standard image with a small C drive and large D drive so they can easily re-clone the system part of the image on C without destroying the client's personal files on D. Most software allows you to choose the install directory. Anything that violates this is disallowed, and they're a big enough company to have some weight with most vendors.
We have enough headaches trying to support
Firefox
Two versions of IE which have their own iffy bugs
Safari
I'm not sure why we continue to support Safari. Most of our users (corporate) use IE6 or IE7. We try to make sure that things work in both of those.
Maybe not for programming purposes but Chrome w/ Google Reader makes for the most powerful RSS reader. Can handle up to 1500 feeds w/ performance still ok, managing subscriptions still functioning.
I'm using it on my work machine, but that's about it. It's been stable for me, and I like the barebones UI. I'll still switch to Firefox for the web developer extensions however.
I'm liking some of GoogleChrome- the Start page with your 9 most recent is the winner for me. The interface takes a little getting used to, but the speed is impressive, especially with Gmail.
However, it glitches with Java, which rules it out for serious work at the moment. I use FireFox mostly and have Chrome for the "other" websites at work.
I'm considering using GWT on an intranet project and considering suggesting to the users that use Chrome to take advantage of the enhanced Javascript performance. Any AJAX-heavy app would be a great candidate to target Chrome.
At my company, we're not targeting it, but we're definitely paying attention to it. My boss is using it as his primary browser, and I have implemented browser detection for it in our scripts in case we ever to need to target it for some reason.
Chrome has the .png opacity bug where the transparent parts of the .png are a solid color if you try to transition the opacity from 0 to 1. In IE7 the opaque parts are black, and in Chrome, they are white. Today, I decided to go ahead and account for this bug in my JavaScript. I don't really test sites on Chrome that often, but I am actually using it for almost all of my browsing.
I will target Chrome as soon as a stable Linux and OSX client is available.
Targeting Chrome/Chromium right now, I think is like targeting Konqueror web browser. It will get popular, but you should wait to a more stable beta, and/or some Linux and OS X client.
My website statistics shows 3.xx % visitors using Chrome which arrived just few weeks back. And Opera is only 4.xx % which has been around for several years.
Easily you can see that rate at which Chrome is picking up.
You can see how easily Google takes over all areas of your computing world and personal world too.
Since Chrome uses Webkit, it has the same rendering engine and DOM support as Safari (not necessarily the same revision of Webkit though). By testing in Safari, you can generally get by without worrying about Chrome. Any differences you find are probably just bugs that you should file on instead of work around.
However, because Chrome uses a different JS engine, there may be a few incompatibilities with Safari. So, if you're doing anything with JS, you might as well fire up Chrome and see if there's anything obviously wrong.
Generally though, you don't target browsers, you target rendering engines (with their associated DOM support and JS engines).
I am using Google Chrome, so far all the web apps I have work fine in it with no modifications.
No.
Why help Google further build an evil empire? In this particular case it is so obvious that they do not care about users but only obsessed with gathering usage info.
It's not any major player yet