Closed Bug 799765 Opened 13 years ago Closed 13 years ago

Calendar event's "All Day Event?" checkbox stops responding to presses

Categories

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

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: cpeterson, Unassigned)

Details

(Whiteboard: [label:calendar] [b2g-desktop-build])

I have not tested this on a phone, so perhaps this is just a problem when using the B2G desktop build with a mouse STR: 1. Open Calendar app 2. Add new event 3. Click mouse down within the "All Day Event?" checkbox, drag a little BUT still within the checkbox, then mouse up. 4. See that the checkbox state is not toggled. 5. WITHOUT moving the mouse, try clicking mouse down/up at the same spot of checkbox. RESULT: The checkbox stops toggling its state after one click. If you move the mouse, then the checkbox will respond to one mouse click, but stop after that.
I don't observe this on my otoro. If you do notice this on a real device please bump up the priority and mark blocking ?
Whiteboard: [label:calendar] → [label:calendar] [b2g-desktop-build]
I tried to reproduce this, but I have a few comments: Step 3: It seems like it only detects a drag not a click Step 5: The checkbox doesn't seem to respond if you keep clicking with a moderate speed (double click perhaps?) , when I click with intervals of 1 second all seems to be fine. These are just my findings based on functional tests, this issue will still require some debugging to confirm this.
Further investigation in the code shows me the 'change' event is triggered. MDN documents that a change event will require the element to loose focus; https://developer.mozilla.org/en-US/docs/Mozilla_event_reference/change This is in line with the assumption made in my previous comment for step 3.
This page has recently undergone a lot of refactoring and I am not seeing this. Please reopen with STR and a video if you are still seeing this with the latest master.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.