894766 - [Buri][Calendar]The screen displays incorrect when viewing the events from the status bar one by one

Status: RESOLVED DUPLICATE of bug 874156

(Firefox OS Graveyard :: Gaia::Calendar, defect, P1)

Description

[sync-1]

SW171
 AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.152
 Firefox os  v1.1
 Mozilla build ID:20130702230206
 
 Created an attachment (id=461462)
 PR pic
 
 DEFECT DESCRIPTION:
 The screen displays incorrect when viewing the events from the status bar one by one.
 REPRODUCING PROCEDURES:
 1.Launch Calendar app -> create an event with reminder -> calendar comes,don't view it form status bar -> then to edit this event from Calendar app,save it -> calendar reminder comes again(Now it have two reminders in status bar)    -> view them successively -> the screen displays abnormally when view the second reminder -> KO
 
 EXPECTED BEHAVIOUR:
 It should display normally when viewing the reminder.
 
 ASSOCIATE SPECIFICATION:
 TEST PLAN REFERENCE:
 TOOLS AND PLATFORMS USED:
 USER IMPACT:
 Mid
 REPRODUCING RATE:
 5/5
 For FT PR, Please list reference mobile's behavior:

Comment 1

[sync-1]

Clone from brother

Comment 2

[sync-1]

Attachment: PR pic

Comment 7

[Jason Smith [:jsmith]]

The screenshot here looks incorrect. Can you fix this?

Comment 8

[Jason Smith [:jsmith]]

(In reply to Jason Smith [:jsmith] from comment #7)
> The screenshot here looks incorrect. Can you fix this?

Found one of the dupes had the right screenshot - https://bug894769.bugzilla.mozilla.org/attachment.cgi?id=776903.

Comment 9

[Jason Smith [:jsmith]]

Same problem as bug 874156.

Comment 10

[buri.blff]

Attachment: 1.PNG

Comment 11

[buri.blff]

(In reply to Jason Smith [:jsmith] from comment #7)
> The screenshot here looks incorrect. Can you fix this?

we has add the correct screenshot, '1.PNG'

Comment 12

[buri.blff]

Please update status, thanks

Comment 13

[Jason Smith [:jsmith]]

(In reply to buri.blff from comment #12)
> Please update status, thanks

Based on the screenshot I'm seeing here, I think that definitely confirms this is a duplicate of bug 874156.