Closed Bug 931729 Opened 6 years ago Closed 6 years ago

[HW test] async dual alert cause settimeout invalid

Categories

(Firefox OS Graveyard :: Gaia, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: tjao, Assigned: tjao)

References

Details

Attachments

(1 file)

I found that if you call another alert asynchronously AFTER you already calls an alert but not closed yet, the following settimeout will not works.
There're some examples in UItest and should be fixed.


For example:
notification.onclose = alert1;
notification.onclick = alert2;

When you click on a notification it will triggers alert2. And when the notification automatically disappeared (closed) it will triggers alert1.
Assignee: nobody → tjao
Blocks: eng-mode
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Attachment #825744 - Flags: review?(flin)
Attachment #825744 - Flags: review?(flin) → review+
merged to gaia-master https://github.com/mozilla-b2g/gaia/commit/6b2b7030364a63d3da31800fe5218f16d55200a8

thanks!
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.