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)
Tracking
(blocking-b2g:-, b2g1828+)
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.
Comment 1•12 years ago
|
||
This is not hard but keep in mind we also have 4 (feb), 5 and 6 week months.
Reporter | ||
Comment 2•12 years ago
|
||
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.
Reporter | ||
Updated•12 years ago
|
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
Reporter | ||
Updated•12 years ago
|
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
Updated•11 years ago
|
Whiteboard: visual design → visual design, UX P2, [TEF_REQ]
Comment 4•11 years ago
|
||
Hi Sam, do you think you can fix this bug?
Comment 5•11 years ago
|
||
Not tracking, polish - if a low risk fix is available please renominate along with approval nomination.
Assignee | ||
Comment 6•11 years ago
|
||
can't see the bug here ? Please provides more infos.
Flags: needinfo?(sjochimek) → needinfo?(epang)
Comment 7•11 years ago
|
||
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)
Assignee | ||
Comment 8•11 years ago
|
||
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)
Comment 9•11 years ago
|
||
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)
Comment 10•11 years ago
|
||
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)
Assignee | ||
Comment 11•11 years ago
|
||
Attachment #758027 -
Flags: feedback?(epang)
Assignee | ||
Comment 12•11 years ago
|
||
Attachment #758028 -
Flags: review?(jlal)
Comment 13•11 years ago
|
||
Comment on attachment 758027 [details]
6 rows month
Looks good, thanks Sam!
Attachment #758027 -
Flags: feedback?(epang) → feedback+
Comment 14•11 years ago
|
||
(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 15•11 years ago
|
||
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)
Assignee | ||
Comment 16•11 years ago
|
||
Comment on attachment 758028 [details]
Github PR
I have updated the PR. Thanks.
Attachment #758028 -
Flags: review?(jlal)
Comment 17•11 years ago
|
||
Comment on attachment 758028 [details]
Github PR
awesome work!
Attachment #758028 -
Flags: review?(jlal) → review+
Comment 18•11 years ago
|
||
in master https://github.com/mozilla-b2g/gaia/commit/a7f7ba9b2700dfff4af102b325a1c9d71ffd6b28
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 19•11 years ago
|
||
looks this PR made travis failed. Sam could you check it? https://travis-ci.org/mozilla-b2g/gaia/builds/7871377
Assignee | ||
Comment 20•11 years ago
|
||
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)
Comment 21•11 years ago
|
||
Going to back out this out for now
Comment 22•11 years ago
|
||
reverted here: https://github.com/mozilla-b2g/gaia/commit/6a97fe462c380867e163ba9be588bc2439eec012. Fairly sure this is a zindexing thing.
Comment 23•11 years ago
|
||
Reopening per backout in comment 22
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 24•11 years ago
|
||
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)
Assignee | ||
Updated•11 years ago
|
Attachment #760315 -
Attachment is obsolete: true
Comment 25•11 years ago
|
||
Sam, can you look into what went wrong here? Thanks!
Flags: needinfo?(sjochimek)
Assignee | ||
Comment 26•11 years ago
|
||
Attachment #758028 -
Attachment is obsolete: true
Attachment #803783 -
Flags: review?(jlal)
Flags: needinfo?(sjochimek)
Assignee | ||
Comment 27•11 years ago
|
||
Attachment #758027 -
Attachment is obsolete: true
Comment 28•11 years ago
|
||
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 29•11 years ago
|
||
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 30•11 years ago
|
||
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)
Updated•11 years ago
|
Flags: needinfo?(sjochimek)
Comment 31•11 years ago
|
||
(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!
Updated•11 years ago
|
Whiteboard: visual design, UX P2, [TEF_REQ] → visual design, UX P2, [TEF_REQ], jian
Updated•11 years ago
|
blocking-b2g: --- → 1.3?
Comment 32•11 years ago
|
||
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.
Comment 33•11 years ago
|
||
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? → -
Assignee | ||
Comment 34•11 years ago
|
||
Comment on attachment 803783 [details]
New PR Github
I have updated the PR.
Attachment #803783 -
Flags: review?(gaye)
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(sjochimek)
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(sjochimek)
Assignee | ||
Updated•11 years ago
|
Attachment #803783 -
Flags: review?(gaye) → review?(kgrandon)
Comment 35•11 years ago
|
||
Attachment #8339057 -
Flags: feedback?(sjochimek)
Comment 36•11 years ago
|
||
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 37•11 years ago
|
||
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)
Assignee | ||
Comment 38•11 years ago
|
||
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)
Assignee | ||
Updated•11 years ago
|
Attachment #8339057 -
Attachment is obsolete: true
Attachment #8339057 -
Flags: feedback?(sjochimek)
Comment 39•11 years ago
|
||
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)
Updated•11 years ago
|
Attachment #8339057 -
Attachment is obsolete: false
Comment 40•11 years ago
|
||
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+
Comment 41•11 years ago
|
||
Landed in master: https://github.com/mozilla-b2g/gaia/commit/fba3b72b9e5feb21128cfd97a4af656d0c0f0df7
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•