You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@cvrebert I didn't file this issue because @suralc already mentioned it.
I'm using latest stable Firefox on LG Optimus 2X with Android 2.3. Tried with latest BS.
I dug into this using Firefox remote debugging on a Nexus 4. It turns out the default user agent stylesheet for Android Firefox 22.0 uses a background-image to style the button elements. I created a page with a single <button> and nothing else in the document and looked at the button's computed style. Here is the relevant output:
@cvrebert Is this a bug? Is there a spec that specifies how user agents should style elements? Using a background gradient is annoying since it's different from all other user agents, but it's not broken.
@cvreberthttps://github.com/cvrebert Is this a bug? Is there a spec
that specifies how user agents should style elements? Using a background
gradient is annoying since it's different from all other user agents, but
it's not broken.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8702#issuecomment-21993196
.
@zdroid I wouldn't call this a "bug". It could be filed as an improvement for the sake of making Android Firefox conform to convention, but styles don't appear to be a standard.
The default style sheet for HTML 4 provided by the W3C says, "Developers are encouraged to use it as a default style sheet in their implementations." It doesn't say it's a standard though; styling is up to the user agent.
The HTML5 spec gives suggested styles for elements, like the <h1>, but again they say they are suggestions.
@tagliala nor Linux is officialy supported (what I think is bad), but if there are known issues, at least we should warn of them to provide a decent user experience. I understand we have not enough community to test everything in all browsers, but if we mantain IE8 support, we cannot totally ignore emerging platforms.
Activity
zlatanvasovic commentedon Jul 28, 2013
@cvrebert I didn't file this issue because @suralc already mentioned it.
I'm using latest stable Firefox on LG Optimus 2X with Android 2.3. Tried with latest BS.
cvrebert commentedon Jul 28, 2013
OK, marking as "confirmed" then.
zlatanvasovic commentedon Jul 28, 2013
:)
2013/7/28 Chris Rebert notifications@github.com
Zlatan Vasović - ZDroid
ssorallen commentedon Jul 28, 2013
I dug into this using Firefox remote debugging on a Nexus 4. It turns out the default user agent stylesheet for Android Firefox 22.0 uses a
background-imageto style the button elements. I created a page with a single<button>and nothing else in the document and looked at the button's computed style. Here is the relevant output:Bootstrap 3.0 only sets
background-color, which means Firefox on Android's default background-image gradient sticks around.To fix this, Bootstrap could set
background-image: noneon thebtnclass.ssorallen commentedon Jul 28, 2013
To confirm the fix of adding
.btn { background-image: none; }, I added a new CSS rule in JS.BEFORE

AFTER
cvrebert commentedon Jul 28, 2013
@ssorallen Nice work!
I wonder whether this would be appropriate for normalize.css.
zlatanvasovic commentedon Jul 29, 2013
Yea. Good idea Chris. It can go to Normalize.
2013/7/29 Chris Rebert notifications@github.com
tagliala commentedon Aug 2, 2013
I should open a new issue but it's the same one.
Please do not forget about
textareaandinputDefault
With
cvrebert commentedon Aug 2, 2013
So, has anyone filed a bug about this with Mozilla like necolas asked?
ssorallen commentedon Aug 2, 2013
@cvrebert Is this a bug? Is there a spec that specifies how user agents should style elements? Using a background gradient is annoying since it's different from all other user agents, but it's not broken.
zlatanvasovic commentedon Aug 2, 2013
https://bugzilla.mozilla.org/show_bug.cgi?id=900871
2013/8/2 Ross Allen notifications@github.com
Zlatan Vasović - ZDroid
ssorallen commentedon Aug 2, 2013
@zdroid I wouldn't call this a "bug". It could be filed as an improvement for the sake of making Android Firefox conform to convention, but styles don't appear to be a standard.
The default style sheet for HTML 4 provided by the W3C says, "Developers are encouraged to use it as a default style sheet in their implementations." It doesn't say it's a standard though; styling is up to the user agent.
The HTML5 spec gives suggested styles for elements, like the
<h1>, but again they say they are suggestions.zlatanvasovic commentedon Aug 2, 2013
@ssorallen It's UX bug... improvment.
tagliala commentedon Aug 2, 2013
tagliala commentedon Aug 2, 2013
@cvrebert
select multipleneeds some tweaking, too.I will let you know and provide screenshots asap. Do you prefer this thread or the other one in normalize.css repo for feedbacks?
6 remaining items
mdo commentedon Aug 3, 2013
So what's the deal here then? Do we need to override some styles or is this all browser bugs and Normalize?
ssorallen commentedon Aug 3, 2013
@mdo It's not a bug. The change belongs in Normalize.
mdo commentedon Aug 3, 2013
Groovy. Thanks so much @ssorallen.
ggam commentedon Aug 14, 2013
Until normalize gets updated, shouldn't we add a note in the docs, perhaps with a link to this issue?
tagliala commentedon Aug 14, 2013
@ggam I suppose there is no mention because firefox mobile is not officially supported
ggam commentedon Aug 14, 2013
@tagliala nor Linux is officialy supported (what I think is bad), but if there are known issues, at least we should warn of them to provide a decent user experience. I understand we have not enough community to test everything in all browsers, but if we mantain IE8 support, we cannot totally ignore emerging platforms.
cvrebert commentedon Aug 15, 2013
Fixed by #9567 / 4d527ec.
(less) fixes twbs#8702 until Normalize.css starts handling this
cvrebert commentedon Sep 22, 2014
Looks like Mozilla came to their senses and are shipping a fix for this in Android Firefox 35 (with regard to gradients).
Remove #8702 entry from Wall of browser bugs
Remove twbs#8702 entry from Wall of browser bugs
(less) fixes twbs#8702 until Normalize.css starts handling this