Closed
Bug 914073
Opened 11 years ago
Closed 11 years ago
[B2G][Helix][camera][ouyangming] The camera UI is error when delete the picture during the calling period
Categories
(Firefox OS Graveyard :: Gaia::Camera, defect, P2)
Firefox OS Graveyard
Gaia::Camera
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: lecky.wanglei, Unassigned)
Details
Attachments
(1 file)
97.90 KB,
image/png
|
Details |
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; aff-kingsoft-ciba; .NET4.0C; .NET4.0E)
Steps to reproduce:
1. Use the device A to call the device B, and device B answer the call, and then press the home key to show the homescreen, just hold on.
2. Open the camera App on device B, take a photo, On the top left corner of the screen will show the photo, click it.
3. After step 2, it will show the photo on screen, on the buttom of the screen will show the "camera","share" and "delete" icon. Click the "delete" icon, and it will show the confirm UI.
My Build Info as following:
gaia:c0ea0a4943dc8d3751b07f5b5c5d3abe06364a14
gecko:170f9e477571127cd40997fa2abe262ed43f0e4d
Actual results:
When show the confirm UI, the three icon(camera,share and delete) were shown too. please refer the attached file.
Expected results:
When show the confirm UI, the three icon(camera,share and delete) should be hiddened. If the device B is not on calling, do the step 2 and 3, it is ok, the user will not see the three icon mentioned above when show the confirm UI.
Severity: normal → blocker
blocking-b2g: --- → hd?
Priority: -- → P2
Comment 1•11 years ago
|
||
This bug looks familiar.
We use confirm to show the dialog. So, cc alive in to check if it is already fixed.
Comment 3•11 years ago
|
||
Is this still reproducible on master?
Hi Wayne,
This bug looks is solved in master, but it exist in V1.1 HD, Can you help us to check it?
If solved in master, Please help us to push to merge this case into V1.1 HD. It blocked the Helix Device .If you can not resolve it , please get the authorization from carrier.
Thanks.
Flags: needinfo?(wchang)
Comment 5•11 years ago
|
||
No plan to uplift this to v1.1/HD given the bug nature it does not block v1.1HD.
Severity: blocker → normal
blocking-b2g: hd? → ---
Flags: needinfo?(wchang)
Hi Beatriz Rodriguez,
If this issue is not be solved on V1.1HD, Do you accept it?
Thanks
Flags: needinfo?(brg)
Comment 7•11 years ago
|
||
(In reply to lecky from comment #6)
> Hi Beatriz Rodriguez,
>
> If this issue is not be solved on V1.1HD, Do you accept it?
>
yes, we accept 1.1 as it is.
Flags: needinfo?(brg)
Comment 8•11 years ago
|
||
The UI has been refreshed since this bug was filed and the problem does not reproduce anymore
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•