Closed Bug 805133 Opened 12 years ago Closed 11 years ago

[Calendar] Calendar month view jumps between 5 and 6 rows (weeks), looks odd

Categories

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

All
Other
defect

Tracking

(blocking-b2g:-, b2g1828+)

RESOLVED FIXED
blocking-b2g -
Tracking Status
b2g18 28+ ---

People

(Reporter: padamczyk, Assigned: sjochimek)

Details

(Keywords: polish, Whiteboard: visual design, UX P2, [TEF_REQ], jian)

Attachments

(6 files, 4 obsolete files)

The calendar rows should be the same height each month, which means 7 rows of weeks.
This is not hard but keep in mind we also have 4 (feb), 5 and 6 week months.
I might have made a typo, cause no month should hit 7 rows. 5 & 6 are the common ones.
Maintaining 6 rows constantly would be the ideal solution, the extra pixel space is nice, but having smoother transitions (layout not shifting) is more desired, it just makes the calendar feel more solid.

In the case of 4 rows. You'd have row 2-5 be the current month. While 1 & 6 are the previous and next.
Summary: [Calendar] Calendar month view jumps between 6 and 7 rows (weeks), looks odd → [Calendar] Calendar month view jumps between 5 and 6 rows (weeks), looks odd
Priority: -- → P3
Spoke with Vicky the visual designer of the app and conferred with Patryk.
This is what needs to happen: 
The cell size will remain the same. i.e. Maintain the size of 5 rows currently (a much more pleasing square shape).
Remove the date stamp in the bottom section(orange).
When you have a month with 6 weeks an extra line (week) is added to the bottom of the month view box, see link:
 
https://www.dropbox.com/s/n5og0ikj6qapta1/Calendar_0002_1c%28Month%29-6weeks.png

Transitions refer to transition document
Whiteboard: visual design → visual design, UX P2, [TEF_REQ]
Hi Sam, do you think you can fix this bug?
Assignee: nobody → sjochimek
tracking-b2g18: --- → ?
Flags: needinfo?(sjochimek)
Not tracking, polish - if a low risk fix is available please renominate along with approval nomination.
can't see the bug here ? Please provides more infos.
Flags: needinfo?(sjochimek) → needinfo?(epang)
Attached image Calender 6 Rows
Hi Sam, from reading the comments -- when a month has 6 lines another row should be added instead of shrinking vertically (into the space of 5). Let me know if you have any questions. Thanks!
Flags: needinfo?(epang) → needinfo?(sjochimek)
Eric, can you provide a screenshot with the 'day title' and events in the list. 
Because when i set the row the same height as for a 5 weeks month, 
the calendar takes a lot of space.
Flags: needinfo?(sjochimek) → needinfo?(epang)
Attached image Calendar 5 and 6 rows
Hi Sam,
Here's a mock up of 5 and 6 rows side by side.  

Victoria, before Sam works on this, can you confirm if this is how this should be implemented? Thanks!
Flags: needinfo?(epang) → needinfo?(vpg)
Yes, that's how it should work. Moreover the orange subtitle with the date should not be there, and days in the future should be white background, while days on the past are light grey, days not corresponding to this month are medium grey and "Today" slot should be dark grey, I assume this is being solved in another bug.
Flags: needinfo?(vpg)
Attached image 6 rows month (obsolete) —
Attachment #758027 - Flags: feedback?(epang)
Attached file Github PR (obsolete) —
Attachment #758028 - Flags: review?(jlal)
Comment on attachment 758027 [details]
6 rows month

Looks good, thanks Sam!
Attachment #758027 - Flags: feedback?(epang) → feedback+
(In reply to Eric Pang [:epang] from comment #13)
> Comment on attachment 758027 [details]
> 6 rows month
> 
> Looks good, thanks Sam!

The 6 rows looks good.  But Visual design is really off with the calendar.  I'm going to open a separate bug to address the visual issues.
Comment on attachment 758028 [details]
Github PR

Hey Sam,

This works great on our launch devices but something about the math that calculates the height of the month area is wacky on the higher resolution devices (you can see this on the GS Peak or by changing the resolution on FF nightly)

Can you reset flag for review again when this is resolved?
Attachment #758028 - Flags: review?(jlal)
Comment on attachment 758028 [details]
Github PR

I have updated the PR. Thanks.
Attachment #758028 - Flags: review?(jlal)
Comment on attachment 758028 [details]
Github PR

awesome work!
Attachment #758028 - Flags: review?(jlal) → review+
in master https://github.com/mozilla-b2g/gaia/commit/a7f7ba9b2700dfff4af102b325a1c9d71ffd6b28
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
looks this PR made travis failed. Sam could you check it?
https://travis-ci.org/mozilla-b2g/gaia/builds/7871377
Attached file Followup PR (fix test) (obsolete) —
Thanks Yuren.

Here is a followup: https://github.com/mozilla-b2g/gaia/pull/10288
James: Can you review it please ?
Attachment #760315 - Flags: review?(jlal)
Attached image borked months day view
Going to back out this out for now
Reopening per backout in comment 22
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment on attachment 760315 [details]
Followup PR (fix test)

resetting flag- sorry should have found this in the first run forgot to open settings panel
Attachment #760315 - Flags: review?(jlal)
Attachment #760315 - Attachment is obsolete: true
Sam, can you look into what went wrong here? Thanks!
Flags: needinfo?(sjochimek)
Attached file New PR Github (obsolete) —
Attachment #758028 - Attachment is obsolete: true
Attachment #803783 - Flags: review?(jlal)
Flags: needinfo?(sjochimek)
Attached image 6 rows month
Attachment #758027 - Attachment is obsolete: true
Comment on attachment 803783 [details]
New PR Github

One of you up for this?
Attachment #803783 - Flags: review?(kgrandon)
Attachment #803783 - Flags: review?(jlal)
Attachment #803783 - Flags: review?(gaye)
Comment on attachment 803783 [details]
New PR Github

I might provide some comments, but will let Gareth review this one.
Attachment #803783 - Flags: review?(kgrandon)
Comment on attachment 803783 [details]
New PR Github

Thanks for the patch Sam. It's very close to ready I think. Flag me again once you get a chance to look at the changes I suggested and questions I asked!
Attachment #803783 - Flags: review?(gaye)
Flags: needinfo?(sjochimek)
(In reply to Gareth Aye [:gaye] from comment #30)
> Comment on attachment 803783 [details]
> New PR Github
> 
> Thanks for the patch Sam. It's very close to ready I think. Flag me again
> once you get a chance to look at the changes I suggested and questions I
> asked!

Hey Sam, can you look at the suggestions and questions Gareth asked? Thanks!
Whiteboard: visual design, UX P2, [TEF_REQ] → visual design, UX P2, [TEF_REQ], jian
blocking-b2g: --- → 1.3?
I don't see why this is nomed 1.3 - new calendar features isn't a priority for 1.3. This shouldn't block that release.
triage: definitely not blocking 1.3, but it looks like it was close a month ago so it would be great if we could get this finished up and landed.
blocking-b2g: 1.3? → -
Comment on attachment 803783 [details]
New PR Github

I have updated the PR.
Attachment #803783 - Flags: review?(gaye)
Flags: needinfo?(sjochimek)
Flags: needinfo?(sjochimek)
Attachment #803783 - Flags: review?(gaye) → review?(kgrandon)
Attached file Github pull request
Attachment #8339057 - Flags: feedback?(sjochimek)
Hi Sam,

Here's an approach with no JS changed which uses the new flex CSS stuff. Please let me know what you think! We can either land this or you can take it from here. Thanks!
Comment on attachment 803783 [details]
New PR Github

I would like to explore the display: flex solution above. Please let me know what you think of the PR, clearing review flag for now.
Attachment #803783 - Flags: review?(kgrandon)
Comment on attachment 803783 [details]
New PR Github

Kevin, thanks for you reco.
I think, that's definitively the right way to do it. i kept the .bottom class in order to have the shadow and add bottom: auto; to #view-selector.
Can you check my updated PR ?
Attachment #803783 - Flags: review?(kgrandon)
Attachment #8339057 - Attachment is obsolete: true
Attachment #8339057 - Flags: feedback?(sjochimek)
Comment on attachment 803783 [details]
New PR Github

Hi Sam, thanks for the patch, this looks good. I made one tiny update, and I've applied your changes on top of my original PR.
Attachment #803783 - Attachment is obsolete: true
Attachment #803783 - Flags: review?(kgrandon)
Attachment #8339057 - Attachment is obsolete: false
Comment on attachment 8339057 [details] [review]
Github pull request

Already reviewed in different attachment.
Attachment #8339057 - Attachment description: WIP - Alternative approach → Github pull request
Attachment #8339057 - Flags: review+
Landed in master: https://github.com/mozilla-b2g/gaia/commit/fba3b72b9e5feb21128cfd97a4af656d0c0f0df7
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: