1440003 - Make the handling of min-scale > max-scale in meta viewport tag consistent with other browsers

Status: RESOLVED FIXED

(Core :: Layout, enhancement, P3)

Description

[Botond Ballo [:botond]]

We have some webcompat issues on file that concern pages that specify a meta viewport tag with a min-scale that's larger than the max-scale.

Some relevant comments on the subject:

Bug 1123938 comment 29:

(In reply to Karl Dubost :karlcow from comment #29)
> There are some sites with a specific hack which also renders broken in
> Firefox but not in Chrome or Safari and relies on this hack.
> 
>  <meta name="viewport" id = "viewport" content = "maximum-scale=0.6667;
> width=480"/>
> found for example in https://webcompat.com/issues/3811
> 
> >  Notes: This is use of the width=480, maximum-scale=0.6667 
> > in the viewport tag. This is an interesting "Holy Grail" 
> > for simple web pages that are friendly for the iPhone. 
> > With the introduction of maximum-scale of two-thirds, 
> > now the fonts in the portrait and the landscape orientations 
> > both look the same size. This combination was discovered 
> > by iPhoneWebDev member D. Rich. 
> —
> https://web.archive.org/web/20110821005853/http://www.iphonewebdev.com/
> examples/viewports/viewport-width-480-maximum-scale-6667.html

Bug 1123938 comment 38:

(In reply to David Bokan from comment #38)
> There is also the strange case of: https://webcompat.com/issues/3811 which
> seems to have a hack where maximum-scale < minimum-scale and we differ in
> precedance. Chrome locks scale to the minimum while Firefox locks it to the
> maximum. This seems like it'd be an easy fix and we just have to settle on
> one or the other.

Comment 1

[Jet Villegas (inactive)]

[ Triage 2018/02/21: P3 ]

Comment 2

[Hiroyuki Ikezoe (:hiro)]

I think the case (min-scale > max-scale) will be fixed by bug 1431601.

Comment 3

[Hiroyuki Ikezoe (:hiro)]

Now I confirmed that this issue has been fixed by bug 1431601.  (I did check the site in https://webcompat.com/issues/18557)