Closed
Bug 812556
Opened 12 years ago
Closed 12 years ago
With two events in conflict with the same event, but that do not conflict with each other - stack the events, don't have one event overlay all events (readability)
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jsmith, Assigned: lorchard)
Details
(Keywords: polish, Whiteboard: [interaction] QARegressExclude)
Attachments
(3 files, 1 obsolete file)
Build:
Device - Unagi
Hashes
<project name="gaia" path="gaia" remote="b2g" revision="620399e19efe849b9dddeffe7e11003847f6b268"/>
<project name="releases-mozilla-aurora" path="gecko" remote="mozilla" revision="f423bd0551fcf872eb58064ed72ed2a4aed2c2d2"/>
Steps:
1. Create an event that spans an hour (let's say 11am - 12pm)
2. Create an event that spans a part of that event's time from #1 (let's say 11am - 11:15am)
3. Create an event that spans a different part that event's time from #1 (let's say 11:15am - 11:30am)
4. View the events in the month, week, day views
Expected:
The events should be able to be viewed in a three-way conflict and not overlap each other.
Actual:
One of the smaller events overpowers all of the other events, making it possible to only view one event. This is a regression - I know this wasn't happening before.
Reporter | ||
Updated•12 years ago
|
blocking-basecamp: --- → ?
Keywords: regression
Reporter | ||
Comment 1•12 years ago
|
||
Change one piece I said above - the third event isn't even viewable in the week view. I know this was working before.
Reporter | ||
Comment 2•12 years ago
|
||
Reporter | ||
Comment 3•12 years ago
|
||
Reporter | ||
Comment 4•12 years ago
|
||
Reporter | ||
Comment 5•12 years ago
|
||
This appears to be a general problem that might be deriving from when we choose to show conflicts by layering events on top of one another - another random case of 2 events fails as well with 11am - 12:30pm and 11:15am - 12:15pm.
Updated•12 years ago
|
Assignee: nobody → lorchard
Reporter | ||
Updated•12 years ago
|
Assignee: lorchard → nobody
Summary: Creating and viewing three events in conflict with one another causes one event to overlap over all three events → Creating and viewing two/three events in conflict with one another causes one event to overlap over all three events - making the other events not readable
Reporter | ||
Comment 7•12 years ago
|
||
It's possible also that the week view issue could be a separate bug. Let me know if that's the case.
Assignee | ||
Comment 8•12 years ago
|
||
Trying to understand what the desired layout looks like.
Current logic distinguishes between "conflict" (ie. events with start time within 5 min of each other) and "overlap" (ie. time span coincides with other events in general), and that looks like what's going on here.
"Conflicts" event bars get laid out side-by-side. But, "overlap" events get slightly indented and overlay other events.
So, as described here, there are 2 conflicts (11am-12:30pm & 11:00am-11:15am) and 1 overlap (11:15am-11:30)
Reporter | ||
Updated•12 years ago
|
Summary: Creating and viewing two/three events in conflict with one another causes one event to overlap over all three events - making the other events not readable → Creating and viewing two/three events with at least one conflict causes one event to overlap over the other events - making the other events not readable
Assignee | ||
Comment 9•12 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #7)
> It's possible also that the week view issue could be a separate bug. Let me
> know if that's the case.
Yeah, I think the week view is separate from this. Looks like there's not an overlap - the event is missing entirely
Summary: Creating and viewing two/three events with at least one conflict causes one event to overlap over the other events - making the other events not readable → Creating and viewing two/three events in conflict with one another causes one event to overlap over all three events - making the other events not readable
Reporter | ||
Updated•12 years ago
|
Keywords: regression
Reporter | ||
Comment 10•12 years ago
|
||
Comment on attachment 682535 [details]
3 Way Conflict Week View
Week view is a separate issue. Filing a different bug.
Attachment #682535 -
Attachment is obsolete: true
Reporter | ||
Comment 11•12 years ago
|
||
bug 812567 filed for the week view issue.
Comment 12•12 years ago
|
||
Hi there,
This is how it should should appear:
https://www.dropbox.com/s/cy1dz3145f8qf57/Calendar-DayView-3wayConflict-11-16-12.jpg
Reporter | ||
Comment 13•12 years ago
|
||
(In reply to Casey Yee [:cyee] from comment #12)
> Hi there,
> This is how it should should appear:
> https://www.dropbox.com/s/cy1dz3145f8qf57/Calendar-DayView-3wayConflict-11-
> 16-12.jpg
Ah. Well, apparently we aren't doing that right now then.
Reporter | ||
Updated•12 years ago
|
Summary: Creating and viewing two/three events in conflict with one another causes one event to overlap over all three events - making the other events not readable → With two events in conflict with the same event, but that do not conflict with each other - stack the events, don't have one event overlay all events (readability)
Reporter | ||
Comment 14•12 years ago
|
||
After digging into this, knowing that this functionally correct, but is a bit of a weird rendering issue, I'm removing the basecamp nom - probably wouldn't block on this, even though I want it.
blocking-basecamp: ? → ---
Keywords: polish
Whiteboard: [interaction][label:polish] → [interaction]
Assignee | ||
Comment 15•12 years ago
|
||
Pointer to Github pull-request
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•12 years ago
|
Whiteboard: [interaction][qa-] → [interaction]
Comment 16•12 years ago
|
||
Unagi, build ID:20130113070202
I was able to reproduce this issue only when 2 of not conflicting with each other events span for 15 minutes each (in the same 30 minutes period), and conflicting with the 3rd event - as it is specified in steps.
I have created a separate bug https://bugzilla.mozilla.org/show_bug.cgi?id=830180 for this issue.
In the situation when 2 of not conflicting with each other events span 30 min and conflicting with the 3rd event, all the events are displaying correctly
No longer blocks: 830180
Whiteboard: [interaction] → [interaction] QARegressExclude
You need to log in
before you can comment on or make changes to this bug.
Description
•