Open Bug 1099411 Opened 6 years ago Updated 5 years ago

[Calendar] Tapping the day tap repeatedly causes the screen to flash black

Categories

(Core :: Layout, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

blocking-b2g -
Tracking Status
b2g-v2.0 --- unaffected
b2g-v2.1 --- affected
b2g-v2.2 --- unaffected

People

(Reporter: rmead, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [2.1-exploratory-3])

Attachments

(1 file)

Attached file Flame2.1logcat.txt
Description:
While on the 'Calendar' app, if you tap the day tab once, every time you tap it after the initial tap the screen will flash black.
   
Repro Steps:
1) Update a Flame device to BuildID: 20141114001204
2) Tap 'Calendar' app
3) Tap 'Day' tap
4) Tap 'Day' tap again
  
Actual:
The page will rescroll through the different times and flash black
  
Expected: 
Either the times rescroll without a black box flashing or the Day tab should do nothing
  

Flame 2.1(319mb)(KitKat)(Shallow Flash)

Environmental Variables:
Device: Flame 2.1
BuildID: 20141114001204
Gaia: af6533781356acc62b0f40c9e040aa5b47d3b709
Gecko: 551326425826
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

  
Repro frequency: 100%
See attached: logcat, video - http://youtu.be/hY3-_Tf-SGo
This issue does NOT occur on Flame 2.0(319mb) and Flame 2.2(319mb)

Tapping on the day tap repeatedly doesn't cause a black flash

Flame 2.0

Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash)
Build ID: 20141114000200
Gaia: 28991b28d54fc4ef8112c8fa678bf20f9faca8c8
Gecko: 62294be0fc98
Version: 32.0 (2.0)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Flame 2.2

Device: Flame 2.2 Master (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141114040205
Gaia: 1e300eac2e56d98ad51d414766d031db7d33221f
Gecko: bbb68df450c2
Version: 36.0a1 (2.2) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
[Blocking Requested - why for this release]:

This black flickering fills up the whole page and repros 100% of the time. Also the page has to scroll back into position causing it to seem like the user is on a different page, when they are actually on the same page.
blocking-b2g: --- → 2.1?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
QA Contact: jmitchell
A reverse / fixed window not available, this issue occurs in the first 2.2 build

---------------------------------------------------------------------------------------------
B2g-34 (2.1) Regression Window:

Last Working:
Device: Flame 2.1
Build ID: 20141113112008
Gaia: af6533781356acc62b0f40c9e040aa5b47d3b709
Gecko: 252a33e86472
Version: 34.0 (2.1)
Firmware Version: v188-1

First Broken:
Device: Flame 2.1
Build ID: 20141113180633
Gaia: af6533781356acc62b0f40c9e040aa5b47d3b709
Gecko: 551326425826
Version: 34.0 (2.1)
Firmware Version: v188-1

Gaia/Gecko Swap
Last Working Gaia First Broken Gecko: Issue DOES reproduce
Gaia: af6533781356acc62b0f40c9e040aa5b47d3b709
Gecko: 551326425826
First Broken Gaia Last Working Gecko: Issue does NOT reproduce
Gaia: af6533781356acc62b0f40c9e040aa5b47d3b709
Gecko: 252a33e86472

Gecko pushlog:
http://hg.mozilla.org/releases/mozilla-b2g34_v2_1/pushloghtml?fromchange=252a33e86472&tochange=551326425826

----------------------------------------------------------------------------------------

Not sure but Possibly broken by changeset c486cd17bebb - which includes:

Bug 1097437
Bug 1092842 - this is my most likely cause
Bug 1096913

Can you take a look Roc?
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(roc)
QA Contact: jmitchell
I could, but the first thing I'd do is make builds to verify the exact changeset that caused the regression. Can you do that for me?
Flags: needinfo?(roc)
Flags: needinfo?(nhirata.bugzilla)
Keywords: qawanted
we are not set up to be able to manually revert gecko commits individually - it is a process being worked on but it is not one currently in place
Flags: needinfo?(roc)
Thanks josh! Naoki, from QA is still trying to help with :roc's request here and may be able to comment here once he has a chance to test this.
Repos the issue : 
Gaia      ee1e5462fa4777eaa7950e0d75706be4383ec007
Gecko     git : https://git.mozilla.org/?p=releases/gecko.git;a=commit;h=dd8f90ca875f4ddfede3433c5c6afc15b3c6b4ec
          hg : http://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/19296c34b1ca )
BuildID   20141119173756
Version   34.0
ro.build.version.incremental=eng.nhirata.20141119.165953
ro.build.date=Wed Nov 19 17:00:21 PST 2014

Does not repro the issue : 
Gaia      ee1e5462fa4777eaa7950e0d75706be4383ec007
Gecko     git : https://git.mozilla.org/?p=releases/gecko.git;a=commit;h=f762c8613e9eb2bf972d47e40a7ab8a0905df6e9
          hg : http://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/4ccd3e117f5d )
BuildID   20141119173756
Version   34.0
ro.build.version.incremental=eng.nhirata.20141119.165953
ro.build.date=Wed Nov 19 17:00:21 PST 2014

It appears that the fix from Bug 1092842 seems to be the change.
Flags: needinfo?(nhirata.bugzilla)
Thanks Naoki! BAck to :roc for help on this.
blocking-b2g: 2.1? → 2.1+
Thanks Naoki - clearing QA-Wanted tag, request was completed in comment 7
Keywords: qawanted
Milan, should this be moved over to graphics?
Flags: needinfo?(milan)
Yes, probably.  Thanks for the investigation as to what caused this.  It would be triggered by the scenario where we have a border without rounded corners - can you confirm that's the case?  Adding a small radius should have the problem go away (not suggesting that's the right thing to do in general.)
Component: Gaia::Calendar → Layout
Flags: needinfo?(milan)
Product: Firefox OS → Core
Dylan, can you get someone to confirm whether or not adding the small radius to the border that Milan referred to works around this?
Flags: needinfo?(doliver)
Miller, can you try out the suggestion in comment #11?
Flags: needinfo?(doliver) → needinfo?(mmedeiros)
adding `.day-events > .hour { border-radius:1px }` to the stylesheet fixed the glitch, but I would rather change the view/router logic to not trigger `onactive` multiple times in a row..
Flags: needinfo?(mmedeiros)
Joint triage: decided to minus it. Please re-nominate it again if there is any concern.
blocking-b2g: 2.1+ → -
You need to log in before you can comment on or make changes to this bug.