Within web browsers on mobile devices, I am able to display the Google Picker, and select files.
However, I am unable to navigate into folders.
On Android, when I touch a folder, it selects it. However, when I touch it again, it does nothing. If I double-touch it, it zooms the browser. If I touch-hold, nothing happens.
On iOS, when I touch a folder, it also selects it. However, touching it again, or double-touching, or touch-hold, nothing happens.
Any help would be appreciated.
Related
I have a Progressive Web App which is capable of being added to home screen. When the home screen icon is tapped (on mobile) there is a (kind of) welcome page with icon that appears before opening the actual app.
I have set the background colour of that welcome screen to be blue in menifest.json. I need to make it brown. I have modified the menifest.json file and updated the website. But the mobile seems to have cached it permanently and it is still showing blue.
I have refreshed page many times and added the web app to home screen multiple times. But it is never changing.
I have also changed the cache name in service-worker.js. Yet no luck!
Plug in your device
visit chrome://inspect
Inspect the device / tab you are looking at for your site
In DevTools go to Network tab
Select 'Disable Cache'
Refresh your web app
Then try adding to homescreen
If you get the correct color it's a good indicator that your previous manifest was cached and you should consider a caching strategy, either file re-visioning the manifest.json file (i.e. manifest.12345.json) OR set appropriate headers.
One thing to note: on Android there is no way to update the icon / manifest details once it's added to homescreen - this is a known issue / bug.
I have an application that uses some regular HTML selects to get user information. Occasionally, when using it with Android stock browser, the selects will just stop working. When I click on them, the browser shows them receiving focus, but the options don't appear for me to select. Once this happens, it seems to break all selects that I access on that tab, even on other websites (including Amazon). If I open another tab, selects are working fine, so the problem seems to be limited to the one tab.
Has anyone experienced something similar, or is there perhaps a work-around that I'm not thinking of?
I could try replacing the selects with a custom control, but this would be a lot of work to do across all applications on my site, and I don't see it being that valuable for such a sporadic problem on one browser.
I'm new to Android development and my first application is looking good.
Curious if anyone has ran into problems with admob:
I have a ListFragment that displays a list with ads at the top and bottom of the list. The display is fine and everything runs ok except -
when I click on the ads and after the browser loads up, clicking back does nothing except for "going" back on the browser and it doesn't go back to the app.
Strangely enough this is happening on my Samsung s3 device but not on my HTC device.
This is because Samsung uses their own custom browser (not stock), and its deciding what to do with the back button. I don't think there's anything you can do- their browser has the focus, it gets to decide what to do with all IO. Your app is in the background and doesn't have any say over IO response.
I have a mobile web page which includes an input element of type 'file', to allow users to upload image files to a server. The page works fine on iOS, and on a Nexus 4 (Android 4.2.1) in the Chrome Browser.
When I use a Samsung S3 (Android 4.0.4) with the default browser clicking on the 'Choose file' button opens the image selection dialog as expected, however after I choose an image and close the dialog the web page gets refreshed, so I lose the image that was selected. Has anyone else seen this behaviour? Any suggestions for a workaround?
The input element that I'm using is fairly standard, and looks like this:
<input id="addPhoto" type="file" accept="image/*"/>
Even without the 'accept' attribute I get the same problem.
Have a look a this issue:
https://code.google.com/p/android/issues/detail?id=53088
Basically, what seems to be happening is this:
Android does not have enough memory available for the file-chooser or camera app.
It frees up memory by closing the browser
After the file chooser/camera is closed the browser is opened again, triggering a page refresh, which renders the whole file choosing exercise useless.
It seems to me that this is beyond the control of any browser based solution but I would love to be proven wrong on this assumption.
I'm having the same problem on a phone with Andriod 2.3.6. One of my colleagues does not have the problem on his phone (can't recall what that is running). He suggested it may be a memory issue. If the phone doesn't have enough available memory, the browser might actually be forced to reload the page after selecting the picture, which defeats the purpose. I have not yet been able to confirm that this is the problem, but my phone does have considerably less available memory than his.
You could try this JQuery Method: http://blueimp.github.com/jQuery-File-Upload/
Uploadify also looks promising: http://www.uploadify.com/
Here's a demo of it: http://www.uploadify.com/demos/
I think the problem is not your code, but the default Android browser you are using.
is it possible to tell a mobile browser, that as long as a certain HTML page is displayed, the device should not turn off its screen?
I want to build something like Project Blinkenlights, but every participant brings his/her own pixel. To set each display to a certain color at a given point in time is managable, just let each one open a website that shows a blank page and changes the background to color the screen. I'd use JavaScript to link the devices and have them log into a control server. But having the pixels wink out because the devices go to sleep would somehow break the concept.
A dedicated app would be overkill, and not every passing onlooker would install an app anyway (at least I wouldn't).
Thanks in advance!
I'm pretty sure you can't do that without bundle your webview inside an app. And whatever is the OS. It's all about protecting the user (and his device battery)