Closed
Bug 625883
Opened 14 years ago
Closed 13 years ago
Fix tap highlight on about:home
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: wesj, Assigned: wesj)
Details
Attachments
(2 files, 1 obsolete file)
526 bytes,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
579 bytes,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
Tap highlighting doesn't look right on about:home. For some reason the active style on divs with role="button" isn't applied in the addons area, but works fine in the recent tabs area. Overriding with !important fixes it, but I'm not sure who is overriding the style (i.e. we shouldn't have to do that). The remote tabs button also has an unnecessary outline in highlighted state.
Assignee | ||
Updated•14 years ago
|
Attachment #503957 -
Flags: review?(mark.finkle)
Comment 1•13 years ago
|
||
Comment on attachment 503957 [details] [diff] [review] Patch v1 >diff --git a/chrome/content/content.css b/chrome/content/content.css >+div[role="button"]:active { >+ background-color: #8db8d8 !important; >+ outline: none !important; >+} Using DOMi, I found that this rule is causing the problem: http://mxr.mozilla.org/mobile-browser/source/themes/core/aboutHome.css#159 body[dir="rtl"] #newAddons > div:not(.loading) { background: url("images/arrowleft-16.png") 1% center no-repeat; } This line causes a "background-color: transparent" to be displayed in DOMi. Deleting that property using DOMi allows the normal tap highlight rules to kick in. I assume we need the "!important" for this and other potential background issues. Why limit the override to just div[role="button"] ? Why not all our tap highlight rules? I don't want a "just for about:home" fix
Assignee | ||
Comment 2•13 years ago
|
||
Hm. Didn't know you could run DOMi on Fennec, but I guess for local pages it all works. Thanks! I'm not sure I like doing things this way. One of the things I liked about this approach was that sites COULD override it if they wanted. I guess they still can, but have to !important their own code. I don't mind us setting the example for sites either though by doing our own custom overrides for these about pages where we need to. Also pulled in the unpushed changes from Bug 625082.
Attachment #504738 -
Flags: review?(mark.finkle)
Updated•13 years ago
|
Attachment #504738 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 3•13 years ago
|
||
Pushed: http://hg.mozilla.org/mobile-browser/rev/14063db434f4
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Verified as fixed on: Mozilla /5.0 (Maemo;Linux armv7l;rv:2.0b10pre)Gecko/20110119 Firefox/4.0b10pre Fennec /4.0b4pre and Mozilla /5.0 (Android;Linux armv7l;rv:2.0b10pre) Gecko/20110119 Firefox/4.0b10pre Fennec /4.0b4pre
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 5•13 years ago
|
||
Crud. There was a typo in the above patch.
Attachment #505215 -
Flags: review?(mark.finkle)
Comment 6•13 years ago
|
||
Comment on attachment 505215 [details] [diff] [review] followup -moz-box-shadow -> box-shadow
Attachment #505215 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 7•13 years ago
|
||
pushed follow up to remove moz-box-shadow entirely: http://hg.mozilla.org/mobile-browser/rev/8b2710b52026
Updated•13 years ago
|
Attachment #503957 -
Attachment is obsolete: true
Attachment #503957 -
Flags: review?(mark.finkle)
You need to log in
before you can comment on or make changes to this bug.
Description
•