Obsolete
Status Update
Comments
ga...@gmail.com <ga...@gmail.com> #2
Which device? All devices supported in AOSP run either 4.1 or 4.3 at this point.
no...@gmail.com <no...@gmail.com> #3
Device Samsung Galaxy with android 4.0.4
sy...@gmail.com <sy...@gmail.com> #4
This report applies to an Android-based device, and the issue tracker where you reported it specializes in issues within the Open Source source code of the Android platform.
We are not able to provide support for individual devices. Please report this issue in the support forum for your device, which might be hosted by your device manufacturer or by the operator where you got your device.
We are not able to provide support for individual devices. Please report this issue in the support forum for your device, which might be hosted by your device manufacturer or by the operator where you got your device.
jp...@gmail.com <jp...@gmail.com> #5
[Comment deleted]
le...@wildkatz.org <le...@wildkatz.org> #6
I've seen this too.... user-scalable is totally broken. No cool web applications for android users I guess and since this has been ongoing for over a year now I doubt Google really cares.
dj...@gmail.com <dj...@gmail.com> #7
Well indeed one clever JS solution to rescale the whole page is there :P but yeah that requires isnane amount of processing !
yv...@gmail.com <yv...@gmail.com> #8
> It seems that device-width, initial-scale, minimum-scale, maximum-scale are honored;
> but introducing the user-scalable=no attribute makes it ignore the other attributes
I cannot reproduce that with Android 2.2. Scaling is always possible by double-tapping or pinch gesture, no matter what combination of these attributes I set. To me it seems it's absolutely impossible to prevent page zooming on Android devices. That's a pain for user interfaces that require tapping on the same button multiple times, because it will always scale the page when it shouldn't do, and move the button around under your finger. Maybe we should recommend Mobile Internet Explorer 9.0, has anyone tried that?
> but introducing the user-scalable=no attribute makes it ignore the other attributes
I cannot reproduce that with Android 2.2. Scaling is always possible by double-tapping or pinch gesture, no matter what combination of these attributes I set. To me it seems it's absolutely impossible to prevent page zooming on Android devices. That's a pain for user interfaces that require tapping on the same button multiple times, because it will always scale the page when it shouldn't do, and move the button around under your finger. Maybe we should recommend Mobile Internet Explorer 9.0, has anyone tried that?
jo...@gmail.com <jo...@gmail.com> #9
So, will the scaling issue ever be solved?
Android 4.x still ignores the user-scalable=no attribute :/
Android 4.x still ignores the user-scalable=no attribute :/
bo...@gmail.com <bo...@gmail.com> #10
initial-scale=1 should work as expected, and in conjunction with minimum-scale=1 and maximum-scale=1, makes this equivalent to user-scalable=no
yv...@gmail.com <yv...@gmail.com> #11
It seems like in this issue, nothing works as it *should*.
gh...@gmail.com <gh...@gmail.com> #12
It works on my Nexus S ( version jelly bean 4.1.1 ). It works on both native and Chrome browsers.
ba...@gmail.com <ba...@gmail.com> #13
The proper separator is not a semi-column but a comma.
So in your sample "width=320; initial-scale=0.45; user-scalable=no" everything after "width=320" is ignored.
So in your sample "width=320; initial-scale=0.45; user-scalable=no" everything after "width=320" is ignored.
si...@gmail.com <si...@gmail.com> #14
I can't seem to get viewport to make any difference whatsoever on my Nexus 7. Horribly broken.
[Deleted User] <[Deleted User]> #15
I'm using one Galaxy SIII with native Android 4.0.4 with meta:
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,minimum-scale=1,user-scalable=no" />
It's working perfectly until I change orientation to landscape. When I change the orientation to landscape mode I can zoom the page until I refresh the page again.
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,minimum-scale=1,user-scalable=no" />
It's working perfectly until I change orientation to landscape. When I change the orientation to landscape mode I can zoom the page until I refresh the page again.
ma...@gmail.com <ma...@gmail.com> #16
Droid Razr (4.1.2 Jellybean). Same issue as #14 lisot...@ciandt.com. Everything works and is fine until I change orientation. After orientation change, it's zoomed in and I'm freely able to zoom in and out.
fl...@gmail.com <fl...@gmail.com> #17
I'm using Samsung Galaxy 3/4/Nexus.
the viewport is set : <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, user-scalable=no" />
Initially works good, but sometimes after flipping the device user-scalable get broken. One can zoom in/out when it shouldn't be able to zoom.
the viewport is set : <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, user-scalable=no" />
Initially works good, but sometimes after flipping the device user-scalable get broken. One can zoom in/out when it shouldn't be able to zoom.
sa...@gmail.com <sa...@gmail.com> #18
Amazing to see that...this defect is opened in 2010 and still status is "new" any reason? Why google is not responding or if there is a workaround?
de...@gmail.com <de...@gmail.com> #19
Ages later - same bug on SIII, Android 4.1.2 and S4.
Chrome browser works fine - so I assume Google will not fix it.
Chrome browser works fine - so I assume Google will not fix it.
th...@gmail.com <th...@gmail.com> #20
My guess that they have nothing to do with Default Android Webkit browser (and its bugs) as it is not present in "pure" Android which can be seeing in Nexus devices.
So I'm wondering if this is correct place to blame someone or ask to fix... looks like this should be addressed to developers of "not pure" Android editions which can be seeing in "not Google" devices like Samsung Galaxy, HTC, etc, but who are they? where their bug trackers? or does they (trackers) exists at all? or any kind of support for such problems? IDK......
So I'm wondering if this is correct place to blame someone or ask to fix... looks like this should be addressed to developers of "not pure" Android editions which can be seeing in "not Google" devices like Samsung Galaxy, HTC, etc, but who are they? where their bug trackers? or does they (trackers) exists at all? or any kind of support for such problems? IDK......
si...@gmail.com <si...@gmail.com> #21
It most certainly is present in "pure" Android. It happens on Galaxy Nexus. I'm not sure about newer Nexus devices. It is the default browser for the Galaxy Nexus though. My guess is that it's been abandoned in favor of Chrome.
th...@gmail.com <th...@gmail.com> #22
Indeed, well then... I don't know the logic behind this...
I can tell that it is for some reason is not present in Nexus 4, 7, 10. But present in Nexus S and Galaxy Nexus (maybe more)
I can tell that it is for some reason is not present in Nexus 4, 7, 10. But present in Nexus S and Galaxy Nexus (maybe more)
ma...@gmail.com <ma...@gmail.com> #23
Wow, what a big bug to be open for so long...
te...@gmail.com <te...@gmail.com> #24
Seriously... this is still an issue that needs to be solved...
s....@gmail.com <s....@gmail.com> #25
C`mon GOOGLE fix that crap!
[Deleted User] <[Deleted User]> #26
The mobile world now has an IE6, thanks google.
je...@gmail.com <je...@gmail.com> #27
Sadly, even on the new Nexus 5, "Made for what matters", doesn't seem to matter...
Please!!!!
Please!!!!
ka...@gmail.com <ka...@gmail.com> #28
thank you Google for following the path of Microsoft. Your android stock browser doesn't get updates, unless you update the whole OS, and it sucks! Now developers have to deal with this for generations to come
je...@gmail.com <je...@gmail.com> #29
Preventing bad web design that tries to stop users from zooming in (and out!) is a feature, not a bug.
yv...@gmail.com <yv...@gmail.com> #30
Preventing a carefully designed mobile app to prevent zoom, and thus causing it to break because of accidental double-tap misinterpreted as zoom IS a bug.
But fortunately the Android browser is so outdated and unmaintained that it's entirely meaningless compared to Chrome for Android and Firefox for Android.
But fortunately the Android browser is so outdated and unmaintained that it's entirely meaningless compared to Chrome for Android and Firefox for Android.
ma...@gmail.com <ma...@gmail.com> #31
agree "The mobile world now has an IE6, thanks google."
[Deleted User] <[Deleted User]> #32
Ok, is there a way around this? without using view port attributes, how can we scale?
en...@google.com <en...@google.com>
ch...@gmail.com <ch...@gmail.com> #33
I'm pretty sure this defect is fixed in Crosswalk for Android, which is based on Chromium.
https://crosswalk-project.org/
https://crosswalk-project.org/contribute/building_crosswalk/android_build.html
The Crosswalk project has basically ended but you can still download the last version (23).
https://crosswalk-project.org/blog/crosswalk-final-release.html "
Below is the version string from Crosswalk 23, which seems to respect Meta Viewport "don't scale my page please", at least for me.
browser: Mozilla/5.0 (Linux; Android 6.0.1; SM-G928T Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Crosswalk/23.53.589.4 Mobile Safari/537.36
Below is the version string of Chrome for Android which does not respect the Meta Viewport tag:
browser: Mozilla/5.0 (Linux; Android 6.0.1; SM-G928T Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.83 Mobile Safari/537.36
The Crosswalk project has basically ended but you can still download the last version (23).
Below is the version string from Crosswalk 23, which seems to respect Meta Viewport "don't scale my page please", at least for me.
browser: Mozilla/5.0 (Linux; Android 6.0.1; SM-G928T Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Crosswalk/23.53.589.4 Mobile Safari/537.36
Below is the version string of Chrome for Android which does not respect the Meta Viewport tag:
browser: Mozilla/5.0 (Linux; Android 6.0.1; SM-G928T Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.83 Mobile Safari/537.36
Description
<meta name="viewport" content="width=1024; initial-scale=0.45; user-scalable=no" />
Changing the values of width and initial-scale don't affect anything at all. user-scalable is respected, as is the android-specific target-densityDpi.
Reference implementation is the iOS browser, which honors *-scale and viewport width.