Closed
Bug 1017024
Opened 11 years ago
Closed 11 years ago
[Messages] Bug 963018 change panel's default height and leads the notification mispositioned
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(blocking-b2g:2.0+, b2g-v2.0 fixed)
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | fixed |
People
(Reporter: julienw, Assigned: julienw)
References
Details
(Keywords: regression)
Attachments
(2 files)
After Bug 963018 lands, the notifications in the composer panel are positioned too high and override the recipient panel. See attachment.
This comes because we changed the panel's default height at the end of the review process.
Assignee | ||
Comment 1•11 years ago
|
||
Comment 2•11 years ago
|
||
blocking on this bad regression, hoping joan/Julien to help take this.
blocking-b2g: 2.0? → 2.0+
Comment 3•11 years ago
|
||
Julien - What's the difference between this bug and bug 1017018?
Flags: needinfo?(felash)
Comment 4•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #3)
> Julien - What's the difference between this bug and bug 1017018?
The bug title is wrong depend on the description. I will update it to correct one.
Updated•11 years ago
|
Assignee: nobody → schung
Summary: [Messages] Bug 963018 regresses the localizability of the "To:" string in the recipient panel → [Messages] Bug 963018 change panel's default height and leads the notification mispositioned
Updated•11 years ago
|
Flags: needinfo?(felash)
Assignee | ||
Comment 5•11 years ago
|
||
Yes, sorry for the bad title, I cloned the other bug :(
Assignee | ||
Comment 6•11 years ago
|
||
I noticed the solution while working on bug 1015867, so here it is :)
Assignee: schung → felash
Attachment #8434173 -
Flags: review?(schung)
Comment 7•11 years ago
|
||
Comment on attachment 8434173 [details]
github PR
Thanks for the quick fixing!
Attachment #8434173 -
Flags: review?(schung) → review+
Comment 8•11 years ago
|
||
in master: 075df2f4337fa96ac3ecf38ea66f2246292a58d5
Updated•11 years ago
|
Target Milestone: --- → 2.0 S3 (6june)
You need to log in
before you can comment on or make changes to this bug.
Description
•