Closed
Bug 864642
Opened 11 years ago
Closed 11 years ago
[Calendar] Wrong display of Time span for events in week view
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(blocking-b2g:leo+)
RESOLVED
DUPLICATE
of bug 864398
blocking-b2g | leo+ |
People
(Reporter: leo.bugzilla.gaia, Assigned: gareth.aye)
Details
(Keywords: regression)
Attachments
(5 files)
1. Title : Time span for events in week view is displayed wrongly 2. Precondition : Set the time on the device as 11.00pm 3. Tester's Action : Try to add new event. a. The date of the event should be next day. b. The start time should be 0.00 and end time should be 1.00 c. Save the event. 4. Detailed Symptom (ENG.) : The Time span of the new event in the week view tab will be displayed wrongly. 5. Gaia Version : 4bf6e6fb802aca9d6efd8f45e42852753df19a7a 6. Expected : The time span should be displayed correctly. 7.Reproducibility: Y 1)Frequency Rate : 100%
Comment 1•11 years ago
|
||
Can you attach a screenshot?
Not able to take screenshots. Looks like regression, not able to reproduce the issue in little older versions of gaia.
Comment 5•11 years ago
|
||
Probably busted this during recent fixes. Definitely looks like a regression from the pictures I'm seeing. ==> leo?
blocking-b2g: --- → leo?
Keywords: regression
There also seems to be problem with the event Time span while creating All-Day events. During creating all-day events, the time spans to the previous day to which the event is set.
Comment 9•11 years ago
|
||
Not really sure why I was flagged. I think Gareth recently did some timespan work, so going to CC him here.
Flags: needinfo?(kgrandon)
Updated•11 years ago
|
Assignee: nobody → gareth.aye
blocking-b2g: leo? → leo+
Comment 10•11 years ago
|
||
Blocking as this seems to be a regression per comment# 5 and passing on to Gareth based on comment# 9
Flags: needinfo?(jlal)
Comment 11•11 years ago
|
||
Fixed in bug 864398 I believe.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•