Here's an interesting one; I'm writing a JSFiddle for a friend in order to illustrate using a :before 'content' CSS rule so as to avoid using two background images and thus hindering loadtime and reaction time. But I'm out of the house, so I'm Fiddling on my Nexus 7.
http://jsfiddle.net/kTMe8/2/ (Please disregard my quick-and-dirty solution, I'm just illustrating the point in as few loc as possible)
To the best of my knowledge, this Fiddle should work as expected on a proper computer, but when I click on the .icon to see if I can fake a 'hover' action from my tab, it redirects the page to Facebook's mobile site.
Wuuuut.
There's no linking code in there as far as I can tell -- it's, like, twenty lines max of inactive HTML and CSS. Is this an Android builtin, and if so, how do I disable it on sites I deploy? What is going on?!
Stats:
Stock Android 4.2.(?)
Chrome Beta Browser (Suspicious...?)
Related
I built a very simple web page for online FAQ reference.
This is basically a plain html page with very few css.
When I open it form my PC brawser it looks just fine, also when I open it from different smartphones (in default brawser) it looks cool in all of them.
Now my problems rises when I try to open it inside my mobile app by calling an intent with ACTION_VIEW like this:
startActivity(new Intent(Intent.ACTION_VIEW, Uri.parse("https://my.domain.it:8443/FAQ/")));
In fact this leads to different behaviours depending on the device used to perform this action. Samsung S2 displays it right, but most of the other devices (i.e. Samsung Note, all Galaxys...) display the site much more zoomed than in ordinary brawser's view, also the zoom seems to be somehow 'fixed' as even zooming out the view won't turn it to the regular brawser correct view.
Is there something I can do for this? I've been googling this for a while but couldn't find a single helpful link.
EDIT
I validated the HTML and the CSS with an online validator and it gives "Valid" in both.
Thanks.
Check your site for HTML or CSS errors. Your issue got nothing in common with android really, but the way 3rd party application interpret your HTML/CSS
Sorry that I don't have a example code for you to see. My question is that I have 8 image buttons for my menu and I need to know how to make the image buttons show and not show.
Meaning When you go to the menu on Android it shows 7 buttons and hides the 1 button that's for iOS and when your on the iOS it shows all 8 image buttons. I have search on Google for two days now still lost.
I have one solution for menu buttons: Try this AwesomeMenu link.
You will have to make your own modification according to your requirement.
If you're writing a web app and you need to know if the app is being accessed on an Android device or an iOS device, you should look at the user agent string.
Here's a list of iOS devices and their user agent strings: http://www.enterpriseios.com/wiki/UserAgent (First hit on Google, can't speak for the accuracy).
Here's one for Android devices: http://www.gtrifonov.com/2011/04/15/google-android-user-agent-strings-2/ (again, no idea how accurate; do your own research to be sure).
You just have to look at navigator.userAgent in your JavaScript and figure out what device the user is using. That's a start, anyway. (You'll also want to look at the iOS web app documentation to see Apple's specific meta tags and stuff to make your web app work nicely on iOS, and I'm sure Android has something similar).
Some of the users of my website are telling me they find it annoying when they try to touch certain links and instead of activating the link it zooms into the link and associated metadata (which is made up of a few links).
So how many css pixels of separation are needed between the link and the associated data to stop this behaviour?
I also would like to know that, and eventually a js/css trick to disable it on demand.
You can also have a look at this question :
How to prevent google chrome android browser to display the magnifier when users click a button?
I'm working on a mobile version of the chatroom my website (just a website, not an android application), and the first time I loaded that page on my Motorola DROID everything acted as expected:
click on the input field to select it
tap the same field again to open up the keyboard
start typing
auto complete words are suggested gray-on-white right above the keyboard
After a few refreshes of the page step 4 does not happen! There is no white bar above the keyboard, and no suggestions come up.
I cannot figure out what may be causing it, or how to test it. I downloaded Dolphin browser, and the keyboard behaves correctly the first time, but not the following times (just like default).
All suggestions are welcome.
Edit Apr 8:
As requested a link to the website: http://phantasyrpg.com will redirect to http://mobile.phantasyrpg.com -- you will need to register and visit the "Tavern" from the menu on top left.
Edit Apr 10:
I've created a very empty example that has the same issue:
http://mobile.phantasyrpg.com/test-chat.html I'm also noticing this on other pages as long as the URI is the same -- there's this issue. If there's a GET parameter that's different, suggestions come up correctly.
I'm wondering if there's some setting in my Apache that sends some silly or broken header. But I don't know much about headers.
I've had this happen before... that are workarounds when using a WebView, but AFAIK there's no way to fix this in just a plain site. But basically, there's some sort of cache or something that exists in the browser tab. At first (new tab) auto-complete always works for me. After staying on the same domain in the same tab for a while, it all crashes. For me specifically, after this point the number '7' on the keyboard will sometimes make the browser segfault =\
If you look around the net, you will notice countless bugs filed for the issues showing up in almost all major websites. All complaining the auto-complete stops on Android. I'm pretty it's global, and unstoppable.
Does Android support visually impaired users in the same way as HTML alt tags are used to provide input for screen readers on the web?
If so, what is the best practice to code Buttons and ImageViews etc so they can be read by a screen reader?
I'm not quite clear on your question. The internet browser, or any applications that rely heavily on HTML rendering are not accessible This quote is taken from this blog post.
You can turn on the accessibility features by going to Settings --> Accessibility and checking the box "Accessibility". While the web browser and browser-based
applications do not yet "talk" using these enhancements, we're working on them for upcoming releases.
Android does provide screen reader support for a lot of applications, see this wiki page for a list of applications known to work well with Android using a free and open source screen reader.
I can't find any general guidelines for creating accessible apps but this LinkedIn group may be helpful. I don't have a LinkedIn account though so don't know how active the group is.
The best resource I've found on the Android Accessibility API is this code walk through: https://sites.google.com/site/gdevelopercodelabs/android/accessibility
See http://developer.android.com/guide/practices/design/accessibility.html for plenty of details on writing an accessible app.
The nearest equivalent to HTML's ALT is the contentDescription property - set in code or in XML.
If you are creating you own custom control, you'll need to do a bit more work to specify other details too; more details at the link above.
Most important thing: when you're done, test with TalkBack, the free Android screenreader from Google. (It's pre-installed on some Android models, but you can download from Android Market if you don't already have it.) You should be able to navigate to all the interactive elements in your app using the directional pad alone, and TalkBack should read out appropriate values for all elements as it does so. (It should pick up the contentDescription and read it out here.)
One thing to watch for is that from what I remember, the screenreader only reads out things that you can navigate to, so if you have instructional text on the page, it may not read out, so you may need to ensure that the contentDescription for other controls is suitably descriptive. To be sure, test with TalkBack, and see for you self (er, hear for yourself!) if what is read out makes sense.
(As noted in one of the other replies, although Android has an accessibility API, the Android browser doesn't actually support it (yet), so HTML pages - even properly marked up HTML code - isn't accessible on Android using the default browser. There are a couple of 3rd party browsers that add accessibility to HTML, though, such as the free IDEAL Web Reader app, which appears to wrap the Android HTML control and then add voicing on top of it. Hopefully Android will make their default browser fully accessible in some later release...)