Closed
Bug 859296
Opened 13 years ago
Closed 13 years ago
[Building Blocks] Update styles for "input area"
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(blocking-b2g:leo+, b2g18 fixed)
People
(Reporter: sergiov, Assigned: arnau)
References
Details
Attachments
(3 files)
There's been a change in the styles of the input area. Basically we should remove the inner box and change the gray gradient to white for the background (please refer to the visuals).
| Assignee | ||
Comment 1•13 years ago
|
||
| Assignee | ||
Comment 2•13 years ago
|
||
| Assignee | ||
Updated•13 years ago
|
Attachment #734637 -
Flags: review?(fbsc)
| Assignee | ||
Updated•13 years ago
|
Component: General → Gaia
Updated•13 years ago
|
Attachment #734637 -
Flags: review?(fbsc) → review+
Comment 3•13 years ago
|
||
R+. Merging!
| Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 4•13 years ago
|
||
Comment on attachment 734637 [details]
patch
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.
[Approval Request Comment]
Bug caused by (feature/regressing bug #):
User impact if declined: not matching UX visuals
Testing completed: Yes
Risk to taking this patch (and alternatives if risky): Very low, just CSS changes
String or UUID changes made by this patch:
Attachment #734637 -
Flags: approval-gaia-v1?
Comment 5•13 years ago
|
||
Comment on attachment 734637 [details]
patch
Removing the gaia-approval-v1, as this BB is necessary for the new layout and visuals designed for the MMS implementation.
Later it will be requested the leo+ flag, and I will add the [NO-UPLIFT] whiteboard as the patch will be landed only when all the MMS functionality is ready.
Attachment #734637 -
Flags: approval-gaia-v1?
Updated•13 years ago
|
Whiteboard: [NO_UPLIFT]
Updated•13 years ago
|
Whiteboard: [NO_UPLIFT]
Updated•12 years ago
|
blocking-b2g: leo? → leo+
Updated•12 years ago
|
Flags: in-moztrap-
You need to log in
before you can comment on or make changes to this bug.
Description
•