Closed
Bug 1026924
Opened 10 years ago
Closed 10 years ago
[Flame][Calendar] Current time indicator should be above event detail ( Day view)
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(blocking-b2g:2.0+, b2g-v2.0 verified, b2g-v2.1 verified)
People
(Reporter: pekochen, Assigned: mmedeiros)
References
Details
Attachments
(5 files)
Current time indicator should be above event detail ( Week view) and should be one pixel thin in week view. (Different with Day view)
Reporter | ||
Comment 1•10 years ago
|
||
Hi Miller, Can you please help on this issue? thank you so much Peko
Flags: needinfo?(mmedeiros)
Assignee | ||
Comment 2•10 years ago
|
||
Hi Peko, the 2px line is caused because Flame have a higher resolution and it's rounding the height of the line since we use percentage to position the element "top:39.4312%" might be in the middle of 2 pixels. The way to fix this is to use a 1px "border" instead of setting the background-color on the element itself. Borders should not be rounded by Gecko. Another options is to convert the percentage into an absolute pixel value. (border is simpler to implement but unsure if in the future Gecko will change the behavior for higher resolution devices causing a regression). can you explain better what do you mean with "above event detail"? do you mean that the line should be in between the text and the blue background? - that is not a simple change, in fact it's pretty complex since we would need to split each event into 2 separate elements (one for background color and another just for the text) and the current calendar structure isn't very friendly to this kind of change. Right now we only have the option to put the line behind or on top of the events (background color and text are the same element). Thanks.
Flags: needinfo?(mmedeiros) → needinfo?(pchen)
Assignee | ||
Comment 3•10 years ago
|
||
I think this should block 2.0 since it's a bug introduced by the visual refresh and happens on Flame. I found a simple way to replicate the day view behavior but I think the "arrow/triangle" should also be on top of the colored border, otherwise it looks weird. I'm going to provide a patch pretty soon and also some screenshots showing the new behavior.
Assignee: nobody → mmedeiros
blocking-b2g: --- → 2.0?
Target Milestone: --- → 2.0 S4 (20june)
Assignee | ||
Comment 4•10 years ago
|
||
did some z-index shuffling, since the event background color has 20% alpha you can still see the line (even tho it's passing behind the events). I believe this should be "good enough" but let me know what you guys think. PS: notice that now the "arrow" is above the colored border, which I think makes way more sense than previous behavior and is also properly aligned (before it was 1px to the left)
Attachment #8442142 -
Flags: ui-review?(pchen)
Attachment #8442142 -
Flags: review?(gaye)
Assignee | ||
Comment 5•10 years ago
|
||
new behavior
Reporter | ||
Comment 6•10 years ago
|
||
Comment on attachment 8442142 [details] [review] Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/20695 Hi Miller, The line looks great now. Thanks for your help!! Peko
Attachment #8442142 -
Flags: ui-review?(pchen) → ui-review+
Flags: needinfo?(pchen)
Comment 7•10 years ago
|
||
I can't tell the difference between the before and after :(
Assignee | ||
Comment 8•10 years ago
|
||
Gareth, the difference is that before the line was on top of the text, now the line is behind it. I also aligned the "arrow" properly (1px to the right) and made sure it is on top of the event (before it was behind the events on day view)
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(gaye)
Target Milestone: 2.0 S4 (20june) → 2.0 S5 (4july)
Comment 10•10 years ago
|
||
Comment on attachment 8442142 [details] [review] Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/20695 LGTM!
Attachment #8442142 -
Flags: review?(gaye) → review+
Flags: needinfo?(gaye)
Assignee | ||
Comment 11•10 years ago
|
||
landed on master: https://github.com/mozilla-b2g/gaia/commit/3ba8af193415e274726255ebb286057bd04dd893
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → fixed
Comment 12•10 years ago
|
||
v2.0: https://github.com/mozilla-b2g/gaia/commit/df7005b7a82a0319afd3dcb87032cf6fb9ba1156
Comment 13•10 years ago
|
||
[Environment] Gaia 43226cf5c3ad19728a88b3786595670b6d60e5c6 Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/d0275ba5f438 BuildID 20140701160202 Version 32.0a2 ro.build.version.incremental=94 ro.build.date=Tue May 20 09:29:20 CST 2014 [Result] Pass
Status: RESOLVED → VERIFIED
Comment 14•10 years ago
|
||
This issue has been successfully verified on Flame 2.0: Gaia-Rev 8d1e868864c8a8f1e037685f0656d1da70d08c06 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/c756bd8bf3c3 Build-ID 20141201000201 Version 32.0 Device-Name flame FW-Release 4.4.2 This issue has been successfully verified on Flame 2.1: Gaia-Rev ccb49abe412c978a4045f0c75abff534372716c4 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/18fb67530b22 Build-ID 20141201001201 Version 34.0 Device-Name flame FW-Release 4.4.2
You need to log in
before you can comment on or make changes to this bug.
Description
•