Closed
Bug 828908
Opened 13 years ago
Closed 12 years ago
[Settings] Hints should not be treated as list items
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(b2g18 fixed)
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
b2g18 | --- | fixed |
People
(Reporter: sergiov, Assigned: sjochimek)
Details
(Whiteboard: visual design [UX-P1], TEF_REQ, PRODUCT-DELIGHT, uxbranch, landed in uxbranch)
Attachments
(2 files)
278.70 KB,
image/jpeg
|
Details | |
196 bytes,
text/html
|
sjochimek
:
review+
vingtetun
:
approval-gaia-v1+
|
Details |
Hints are used to provide further info to the user in cases where the action to perform needs further clarification. Taking this into account they should not be treated as "independent" list items and they have to be always displayed underneath the list item they pertain to, without using any divider between them.
Whiteboard: visual design, incorrect implementation → visual design [UX-P1], TEF_REQ
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → sjochimek
Updated•13 years ago
|
Whiteboard: visual design [UX-P1], TEF_REQ → visual design [UX-P1], TEF_REQ, PRODUCT-DELIGHT
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #707579 -
Flags: feedback?(pla)
Flags: needinfo?
Just loaded this and it looks as intended (same as the attachment 'Correct use of Hints :: Screenshot').
Flags: needinfo?
Attachment #707579 -
Flags: feedback?(pla)
Assignee | ||
Comment 3•13 years ago
|
||
landed in uxbranch: https://github.com/gordonbrander/gaia/commit/42ae93a5cc9787e61801f84bfeaedc0fb402ccc0
Whiteboard: visual design [UX-P1], TEF_REQ, PRODUCT-DELIGHT → visual design [UX-P1], TEF_REQ, PRODUCT-DELIGHT, uxbranch, landed in uxbranch
Assignee | ||
Updated•13 years ago
|
Attachment #707579 -
Flags: review+
Assignee | ||
Comment 4•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
verfied on master,
Master build : 2013-03-26-07-02-04
"mozilla-central" revision="28b048ffb7a7"
"integration/gaia-central" revision="44f6a17f24d4"
"gecko.git"revision="a800f14ea7022a78966f7fe14a9b0d11c569b151"
"gaia.git" revision="ace1eb32a313da1232bbdf9cff2581a4b036356d"
Not on v1 train. filing bug on the overlapping text.
Status: RESOLVED → VERIFIED
![]() |
||
Updated•12 years ago
|
status-b2g18:
--- → affected
Comment 6•12 years ago
|
||
Comment on attachment 707579 [details]
branch patch
Is this ready to raise to approval? with user value and risk in the comments? Our goal is to wrap up all Yedo and VxD changes by April 5th.
Assignee | ||
Comment 7•12 years ago
|
||
Comment on attachment 707579 [details]
branch patch
Master commit hash is 6c6cb69
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: -
Testing completed: Yes see #c5
Risk to taking this patch (and alternatives if risky): Only CSS changes and HTML tags.
String or UUID changes made by this patch: -
Attachment #707579 -
Flags: approval-gaia-v1?(21)
Comment 8•12 years ago
|
||
Comment on attachment 707579 [details]
branch patch
This comes from the UX branch process where QA has already checked that it works. a=me.
Attachment #707579 -
Flags: approval-gaia-v1?(21) → approval-gaia-v1+
Comment 9•12 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 -m1 25d9e53380db967d76223c5f1e1940ed907ed447
<RESOLVE MERGE CONFLICTS>
git commit
Comment 10•12 years ago
|
||
(In reply to John Ford [:jhford] from comment #9)
> 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 -m1 25d9e53380db967d76223c5f1e1940ed907ed447
> <RESOLVE MERGE CONFLICTS>
> git commit
Sam, can you please look into this? Thanks!
Flags: needinfo?(sjochimek)
Assignee | ||
Comment 11•12 years ago
|
||
Be careful that master commit hash for this bug is 6c6cb69 (ie. #c7)
Flags: needinfo?(sjochimek) → needinfo?(jhford)
You need to log in
before you can comment on or make changes to this bug.
Description
•