Closed
Bug 902123
Opened 11 years ago
Closed 11 years ago
The background of the landing page is darker once e.me has been opened
Categories
(Firefox OS Graveyard :: Gaia::Homescreen, defect)
Firefox OS Graveyard
Gaia::Homescreen
Tracking
(blocking-b2g:leo+, b2g-v1.2 fixed, b2g-v1.3 fixed, b2g-v1.3T fixed)
VERIFIED
FIXED
blocking-b2g | leo+ |
People
(Reporter: vingtetun, Assigned: vingtetun)
References
Details
Attachments
(1 file)
943 bytes,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
With e.me on the landing page once you have opened it the background of the landing page is darker.
There are UI/UX discussions about if it should always be darker or not...
Assignee | ||
Updated•11 years ago
|
blocking-b2g: --- → leo?
Assignee | ||
Comment 1•11 years ago
|
||
This is a very small CSS fix from evyater that should make 1.1. The risk are really low.
Attachment #787055 -
Flags: review+
Assignee | ||
Comment 2•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 3•11 years ago
|
||
This is being tested alongside bug 838634, so in the unlikely case that this causes a regression, we'll back out.
Comment 4•11 years ago
|
||
Downloaded build from 08062013 and witnessed reported behavior.
Downloaded latest build and witnessed resolved/fixed behavior.
Background is not as dark as previously reported.
Build ID: 20130813041202
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/36bbc5943448
Gaia: df57dcec720493bedff4601499d78c147ad7d253
Platform Version: 18.1
RIL Version: 01.01.00.019.190
Firmware version: D300f08o
Status: RESOLVED → VERIFIED
Keywords: verifyme
Comment 6•11 years ago
|
||
I was not able to uplift this bug to v1-train. If this bug has dependencies which are not marked in this bug, please comment on this bug. If this bug depends on patches that aren't approved for v1-train, we need to re-evaluate the approval. Otherwise, if this is just a merge conflict, you might be able to resolve it with:
git checkout v1-train
git cherry-pick -x 3075fba41a472194bf04a3507d6341e31d416b3f
<RESOLVE MERGE CONFLICTS>
git commit
Flags: needinfo?(nobody)
Comment 7•11 years ago
|
||
This bug was partially uplifted.
Uplifted 3075fba41a472194bf04a3507d6341e31d416b3f to:
v1.2 already had this commit
Commit 3075fba41a472194bf04a3507d6341e31d416b3f didn't uplift to branch v1-train
status-b2g-v1.2:
--- → fixed
Comment 8•11 years ago
|
||
This bug was partially uplifted.
Uplifted 3075fba41a472194bf04a3507d6341e31d416b3f to:
v1.3 already had this commit
Commit 3075fba41a472194bf04a3507d6341e31d416b3f didn't uplift to branch v1-train
status-b2g-v1.3:
--- → fixed
Updated•11 years ago
|
Assignee: nobody → 21
Updated•10 years ago
|
Flags: needinfo?(nobody) → needinfo?
Updated•10 years ago
|
Flags: needinfo?
Updated•10 years ago
|
status-b2g-v1.3T:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•