onFillRequest of AutofillSerive is not triggered on chrome browser in android. I checked in another browser like firefox, it is working fine there. How app like Dashlane support autofill in chrome?
It is a bug in Chrome. The fix should land in Chrome 89.
https://bugs.chromium.org/p/chromium/issues/detail?id=1151614
https://github.com/bitwarden/mobile/issues/489
Related
I have an application configured to support FB authentication, but it seems to be window.fbAsyncInit() didn't gets called from some of my mobile devices whereas it works for desktop and some mobile devices.
Works for : Android(Marshmallow OS) with Default browser
Desktop with Chrome and Firefox
Not works for: IOS with Safari browser
Android(Lollipop) with chrome browser
Does anyone know the reason?
Thanks in advance
My problem is that in my mobile nexus5 with chrome browser, I can launch a native application with a schema or go to another page if failed, everything works well. But in some other mobiles still with chrome browser (in my case, there are mobiles made by manufactories from China like Huawei, they custom their android system like the way HTC and Sumsung do), the browser seems like treating the schema as a http request and open it, and then shows this page cannot be displayed. And also my Javasript code in previous page cannot work anymore.
Is this a bug with chrome or because the android system is modified manufactory so that chrome cannot handle the schema correctly.
I always have issue with the CSS styling in the default Android browser while building my responsive website. What I usually do was doing trials and errors on pc until the problem was solved.
There is a tool for chrome browser:
https://developer.chrome.com/devtools/docs/remote-debugging
but chrome usually display fine for me just that I need a debugging tool for the default Android browser. Is there any solution for this?
I'm not aware of any way to test on the old android browser using remote debugging, as new devices nowadays (Anything post 4.0) have chrome installed by default on Android.
One method you can use to help with testing responsive/mobile sites is using Chrome's mobile emulation tool
Either select a device on that list, or fake out the user agent with something from this page http://www.useragentstring.com/pages/Android%20Webkit%20Browser/
according to Google, filechooser is taken off and no longer working on android 4.4, but why would chrome still working? I have a device that is running android 4.4. My app has a webview, and inside of this webview I have a button which allow user to upload photo. It was working fine until 4.4. my question is that how come Chrome is able to pick up filechooser event but mine is not while both apps(chrome and mine) are running on the same device. what did google do differently? Thanks!
There was a bug which occurred in KitKat which broke the file chooser for both Chrome (https://code.google.com/p/chromium/issues/detail?id=278640) and I believe the WebView was affected by the same problem.
WebView only ever supported a file chooser through a private API (i.e. an API which developers shouldn't use or rely on), which was removed in KitKat.
The WebView team are aware of the number of developers wanting this.
As Kinlan has stated, Chrome for Android doesn't use a WebView.
How can I mimic the Android default browser on my Desktop with Firefox or Chrome? I've noticed that Google's search results, as well as other sites, sometimes look different on the Stock Android browser than other mobile browsers.
Can I change the userAgent to do something like this so I can view things on my desktop as on my phone?