Closed
Bug 938191
Opened 12 years ago
Closed 12 years ago
[B2G][Camera][Thumbnail] Bottom of thumbnail preview contains incorrect UI
Categories
(Firefox OS Graveyard :: Gaia::Camera, defect)
Tracking
(blocking-b2g:1.3+, firefox28 affected)
People
(Reporter: gbennett, Assigned: wilsonpage)
References
Details
(Keywords: regression, smoketest)
Attachments
(2 files)
Description:
At the bottom of a expanded thumbnail there are normally a few buttons (delete, share, camera), but they have been replaced with grey bars that still function.
Repro Steps:
1) Updated Buri 1.3 mozRIL to BuildID: 20131113040200
2) Open camera app
3) Take a picture and view thumbnail
Actual:
Grey bars have replaced the bottom functionality buttons.
Expected:
Delete, share, and camera buttons appear properly.
Environmental Variables:
Device: Buri 1.3 mozRIL
BuildID: 20131113040200
Gaia: 7243b75041c93bc7deb240131748d0b164f3f0b0
Gecko: 7b014f0f3b03
Version: 28.0a1
Firmware Version: 20131104
Repro frequency: 100%
See attached: ThumbnailPreview.zip
Comment 3•12 years ago
|
||
Not able to repro on Buri using:
Gaia 20e8d407dac3bb2ad2616e8c2d8678d70fd82fa0
SourceStamp 3fc449c858e6
BuildID 20131113004000
Version 26.0
Base image: 11-4
Updated•12 years ago
|
Comment 4•12 years ago
|
||
So this was working yesterday, broke today.
Comment 5•12 years ago
|
||
This was broken by either bug 933898 or bug 937385.
Updated•12 years ago
|
Assignee: nobody → dmarcos
Updated•12 years ago
|
Assignee: dmarcos → wilsonpage
Updated•12 years ago
|
blocking-b2g: --- → 1.3?
Updated•12 years ago
|
Keywords: regressionwindow-wanted
| Assignee | ||
Comment 6•12 years ago
|
||
Attachment #831883 -
Flags: review?(dmarcos)
Updated•12 years ago
|
Attachment #831883 -
Flags: review?(dmarcos) → review+
| Assignee | ||
Comment 7•12 years ago
|
||
This was due to incorrect order of CSS files in the <head>, messing with selector cascade order.
No longer blocks: 937385
Comment 8•12 years ago
|
||
(In reply to Wilson Page from comment #7)
> This was due to incorrect order of CSS files in the <head>, messing with
> selector cascade order.
So it was caused by bug 937385 then, right?
(I'm assuming that was a bz conflict that happened there)
Blocks: 937385
Comment 9•12 years ago
|
||
| Assignee | ||
Comment 10•12 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #8)
> (In reply to Wilson Page from comment #7)
> > This was due to incorrect order of CSS files in the <head>, messing with
> > selector cascade order.
>
> So it was caused by bug 937385 then, right?
>
> (I'm assuming that was a bz conflict that happened there)
Yes, sorry about that.
| Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•