Closed
Bug 819127
Opened 12 years ago
Closed 12 years ago
Media queries don't work correctly in Firefox OS browser
Categories
(Firefox OS Graveyard :: Gaia::Browser, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: kairo, Unassigned)
Details
Attachments
(1 file)
1.76 KB,
text/html
|
Details |
When I call up a web page in the Firefox OS browser that uses media queries to fit into different screen sizes, it doesn't actually apply the queries that fit for the 320px wide size that is actually available.
Instead, we seem to make the queries believe we have a screen width between 900px and 1000px - see what the attached testcase shows on a device, it shows all lines up to "900+" to me on my otoro.
Note that this also disagrees with what we are doing in the Responsive Design View in Firefox desktop, where I get "300+" as expected when I set to 320x480.
I hate this behavior too, but all "mobile" browsers lie about their viewport width. Your test shows inflated values in fennec-android, android-browser, and chrome-android. We have to keep this behavior for parity.
(b2g "app" content sees the real viewport.)
If you add <meta name="viewport" value="width=device-width"> you should see the actual values.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
![]() |
Reporter | |
Comment 2•12 years ago
|
||
Needing to add a AFAIK non-standard viewport tag to get standards-compliant behavior from browsers really, really sucks. But I guess that's just how the mobile web is, it sucks from start to end. :(
![]() |
Reporter | |
Comment 3•12 years ago
|
||
That said, to be constructive in *some* way at least, do we have bugs on file to support that wrong but apparently necessary behavior on desktop in the "Responsive Design View" so that at least that view isn't completely useless for mobile design?
![]() |
Reporter | |
Comment 4•12 years ago
|
||
Oh, and another thing, in case anyone looks in here for help with such a problem, the right tag is <meta name="viewport" content="width=device-width"> - meta has name/content attributes, not value. ;-)
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #3)
> That said, to be constructive in *some* way at least, do we have bugs on
> file to support that wrong but apparently necessary behavior on desktop in
> the "Responsive Design View" so that at least that view isn't completely
> useless for mobile design?
Not to my knowledge, but that would be a good idea.
![]() |
Reporter | |
Comment 6•12 years ago
|
||
(In reply to Chris Jones [:cjones] [:warhammer] from comment #5)
> (In reply to Robert Kaiser (:kairo@mozilla.com) from comment #3)
> > That said, to be constructive in *some* way at least, do we have bugs on
> > file to support that wrong but apparently necessary behavior on desktop in
> > the "Responsive Design View" so that at least that view isn't completely
> > useless for mobile design?
>
> Not to my knowledge, but that would be a good idea.
This is now bug 883005.
You need to log in
before you can comment on or make changes to this bug.
Description
•