Closed
Bug 1049685
Opened 11 years ago
Closed 11 years ago
[Tarako][Settings] Ringer's name overlay Alerts in Sound setting page
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:1.3T+, b2g-v1.3T fixed, b2g-v1.4 affected, b2g-v2.0 fixed)
RESOLVED
FIXED
| blocking-b2g | 1.3T+ |
People
(Reporter: seinlin, Assigned: yifan)
References
Details
Attachments
(7 files)
|
24.45 KB,
image/png
|
Details | |
|
46 bytes,
text/x-github-pull-request
|
arthurcc
:
review+
|
Details | Review |
|
15.65 KB,
image/png
|
Details | |
|
46 bytes,
text/x-github-pull-request
|
arthurcc
:
review+
|
Details | Review |
|
46 bytes,
text/x-github-pull-request
|
arnau
:
review-
|
Details | Review |
|
46 bytes,
text/x-github-pull-request
|
arnau
:
review-
|
Details | Review |
|
37.75 KB,
image/png
|
Details |
After ring tone is set from music, Ringer's name overlay Alerts in Sound setting page.
| Reporter | ||
Comment 1•11 years ago
|
||
Hi Evelyn, could you help on this bug? Thanks!
Flags: needinfo?(ehung)
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → yliao
Comment 2•11 years ago
|
||
Yi-fan can help. :)
Updated•11 years ago
|
Flags: needinfo?(ehung)
| Assignee | ||
Comment 3•11 years ago
|
||
Bring text-overflow: ellipsis back and still keep box-shadow hack.
Use text-indent instead of left padding and '... ' instead of ellipsis.
Only for li button.
Attachment #8469775 -
Flags: review?(arthur.chen)
| Assignee | ||
Comment 4•11 years ago
|
||
Fixed result.
Comment 5•11 years ago
|
||
Comment on attachment 8469775 [details] [review]
pull request
Looks good to me, thanks! However, per https://bugzilla.mozilla.org/show_bug.cgi?id=1010675#c80 this should be a platform bug. Based on the decision there, I think we could land this to the tarako branch but not master.
Attachment #8469775 -
Flags: review?(arthur.chen) → review+
| Assignee | ||
Comment 6•11 years ago
|
||
Merged into v1.3t
https://github.com/mozilla-b2g/gaia/pull/22652
Thank you. So according to bug 1010675, this PR might need to be backout once the behavior changes in gecko for v1.3t.
Updated•11 years ago
|
status-b2g-v1.3T:
--- → fixed
Comment 10•11 years ago
|
||
(In reply to Arthur Chen [:arthurcc] from comment #5)
> Comment on attachment 8469775 [details] [review]
> pull request
>
> Looks good to me, thanks! However, per
> https://bugzilla.mozilla.org/show_bug.cgi?id=1010675#c80 this should be a
> platform bug. Based on the decision there, I think we could land this to the
> tarako branch but not master.
Hi Arthur,
Is it a valid issue for master? If so, can we uplift this patch to 1.4/2.0/master and remove the master one once Gecko bug landed?
(In reply to Yi-Fan Liao [:yifan][:yliao] from comment #6)
> Thank you. So according to bug 1010675, this PR might need to be backout
> once the behavior changes in gecko for v1.3t.
@Yi-fan, Gecko for 1.3t should not have any change, so we always need your patch for 1.3t.
| Assignee | ||
Comment 11•11 years ago
|
||
Got it.
There are some style conflicts in the shared/style/button.css between master and v1.3t when applying this patch. If the decision is we need this workaround for the master, I'll make another one.
Flags: needinfo?(yliao) → needinfo?(arthur.chen)
Comment 12•11 years ago
|
||
As there seems no progress in bug 1010675, let's land the workaround to the other branches and add a comment describing that the workaround should be removed once 1010675 gets fixed.
Flags: needinfo?(arthur.chen)
| Assignee | ||
Comment 13•11 years ago
|
||
This PR is the workaround for master branch.
Attachment #8472110 -
Flags: review?(arthur.chen)
| Assignee | ||
Updated•11 years ago
|
status-b2g-v1.4:
--- → affected
status-b2g-v2.0:
--- → affected
| Assignee | ||
Comment 14•11 years ago
|
||
Comment on attachment 8469775 [details] [review]
pull request
Please land this workaround on v1.4, thank you.
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #): 1049685
[User impact] if declined: Button text overlaps other UI elements in settings app when button text is too long
[Testing completed]: https://tbpl.mozilla.org/?rev=0d290adba539a1186c13610584224ec0aa138249&tree=Gaia-Try
[Risk to taking this patch] (and alternatives if risky): None
[String changes made]: N/A
Attachment #8469775 -
Flags: approval-gaia-v1.4?(praghunath)
Comment 15•11 years ago
|
||
Comment on attachment 8472110 [details] [review]
pull request for master branch
r=me, thank you!
Attachment #8472110 -
Flags: review?(arthur.chen) → review+
| Assignee | ||
Comment 16•11 years ago
|
||
| Assignee | ||
Comment 17•11 years ago
|
||
(In reply to Yi-Fan Liao [:yifan][:yliao] from comment #16)
> Merged into master
> https://github.com/mozilla-b2g/gaia/pull/22818
>
> TBPL
> https://tbpl.mozilla.org/
> ?rev=e6ff9dd1f8c05eda816507bab3ad602c7e936b93&tree=Gaia-Try
Backout Commit: c4ba26551979b0293fd168bfcc30d07a5efeed70 [c4ba265]
Found glitches in FTU Date & Time settings.
| Assignee | ||
Comment 18•11 years ago
|
||
Add css selector :not(.change) to exclude 'change' buttons in FTU. To prevent unnecessary ellipsis.
Attachment #8474421 -
Flags: review?(arthur.chen)
| Assignee | ||
Comment 19•11 years ago
|
||
(In reply to Yi-Fan Liao [:yifan][:yliao] from comment #6)
> Merged into v1.3t
> https://github.com/mozilla-b2g/gaia/pull/22652
>
> Thank you. So according to bug 1010675, this PR might need to be backout
> once the behavior changes in gecko for v1.3t.
Backout Commit: 7539f4e52863521efa5acb9f4b285a05f44ee1ac [7539f4e]
Found glitches in FTU Date & Time settings.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Updated•11 years ago
|
Attachment #8469775 -
Flags: approval-gaia-v1.4?(praghunath)
| Assignee | ||
Comment 20•11 years ago
|
||
Revised css to exclude 'change' button ellipsis in date & time settings in FTU.
Attachment #8474479 -
Flags: review?(arthur.chen)
Comment 21•11 years ago
|
||
Comment on attachment 8474421 [details] [review]
pull request for master & 2.0 branch, fixed FTU glitch
Flagging Arnau as the patch involves other selectors.
Attachment #8474421 -
Flags: review?(arthur.chen) → review?(rnowmrch)
Updated•11 years ago
|
Attachment #8474479 -
Flags: review?(arthur.chen) → review?(rnowmrch)
Comment 22•11 years ago
|
||
Hi Arnau, can you help on the patch review? Thank you.
Flags: needinfo?(rnowmrch)
Hey, Sorry it took me so long to look into this, I was on PTO.
In bug 1036147 we allowed multiline for list buttons.
The patched proposed here suggest going back to one line again, which would cause again localization issues like https://bug1036147.bugzilla.mozilla.org/attachment.cgi?id=8452719
I don't have a Tarako to test, but I guess this issue is not happening after landing bug 1036147, right?
My approach would be allowing multiline in previous releases as we now have in master.
I will take a closer look to 1.3
Flags: needinfo?(rnowmrch)
Comment 24•11 years ago
|
||
qawanted, please help to verify if this happens on Flame in 2.1, 2.0 and 1.4? If no, we should close this one since tarako is using 1.3T and it's fixed. Thanks.
Keywords: qawanted
Comment 25•11 years ago
|
||
(In reply to howie [:howie] from comment #24)
> qawanted, please help to verify if this happens on Flame in 2.1, 2.0 and
> 1.4? If no, we should close this one since tarako is using 1.3T and it's
> fixed. Thanks.
Issue is NOT reproducible on Flame KK base only (v1.4), Flame 2.0, and Flame 2.1. Ringtone name properly displays without overlapping.
Tested on:
(Unable to pull correct environmental variables for Flame KK base)
Device: Flame
BuildID: 20140911220254
Gaia: 91dd0e596aa7c124dd968e1474b23e7992dc35a1
Gecko: a66168598533
Version: 32.0 (2.0)
Firmware: v165
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Device: Flame
BuildID: 20140912081053
Gaia: 59e5c2467b7b8219ed194a0d0a94c6ed59af95be
Gecko: b09d2857b74e
Version: 34.0a2 (2.1)
Firmware: v165
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Comment 26•11 years ago
|
||
Testing the 2.0 and 2.1 branches in KK base is fine but 1.4 will be built on JB so we need to test 1.4 there.
QA-Wanted to test 1.4 on JB
Comment 27•11 years ago
|
||
Comment 28•11 years ago
|
||
Issue DOES occur in latest 1.4 Flame on the v123 base image (Jelly Bean).
See attachment: '1.4_v123_screenshot.png'
Environmental Variables:
Device: Flame 1.4
BuildID: 20140910070823
Gaia: 6018a1c18f0c3eab25aac2ba3064904740591dd2
Gecko: 39c9dbc311f7
Version: 30.0 (1.4)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Comment 29•11 years ago
|
||
(In reply to howie [:howie] from comment #24)
> qawanted, please help to verify if this happens on Flame in 2.1, 2.0 and
> 1.4? If no, we should close this one since tarako is using 1.3T and it's
> fixed. Thanks.
1.4 (JB) = Repro
2.0 (KK) = No Repro
2.1 (KK) = No Repro
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(hochang)
Attachment #8474421 -
Flags: review?(rnowmrch) → review-
Attachment #8474479 -
Flags: review?(rnowmrch) → review-
Comment 30•11 years ago
|
||
per offline discussion with Wayne, 1.4 JB can be ignored. Thanks everyone for the help!
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Flags: needinfo?(hochang)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•