Closed
Bug 1009641
Opened 11 years ago
Closed 11 years ago
[B2G][Notifications API][Browser] Closing an already closed notification doesn't throw onerror callback in logcat
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(b2g-v1.4 affected)
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
b2g-v1.4 | --- | affected |
People
(Reporter: rkunkel, Unassigned)
References
Details
(Whiteboard: OpenCrun1.4-3)
Attachments
(1 file)
112.46 KB,
text/plain
|
Details |
Description:
When the user attempts to close an already closed notification, there should be an onerror message displayed in the logcat
Repro Steps:
1) Update an Open_C device to BuildID: 20140512040203
2) Browser > http://mozilla.github.io/qa-testcase-data/webapi/notifications/index.html
3) Request Permission
4) Add a tag 'A' to notification
5) Show notification
6) Get notification 'A' - verify the notification was created
7) Close notification index 0
8) Close notification index 0 again
9) Observe onerror event is not fired in logcat
Actual:
There isn't an onerror callback message in the logcat
Expected:
An onerror callback message is displayed within the logcat
v1.4 Environmental Variables:
Device: Open_C v1.4 MOZ RIL
Build ID: 20140513000208
Gecko: c140bcd02b9b
Gaia: b40103dec34a147c9018a1af76eb21c3184f2f93
Base Image: P821A10V1.0.0B06_LOG_DL
Repro frequency: 100%
Link to failed test case https://moztrap.mozilla.org/manage/case/9944/
See attached: logcat
Reporter | ||
Comment 1•11 years ago
|
||
This issue DOES reproduce on the latest Buri build:
v1.4 Environmental Variables:
Device: Buri v1.4 MOZ RIL
BuildID: 20140512000204
Gaia: 17fb44880e95bc7ae363a609d811bf5a9a067b5b
Gecko: ec24f847e7c0
Version: 30.0
Firmware Version: V1.2-device.cfg
Comment 2•11 years ago
|
||
Anne - The notifications spec doesn't really call out what the right behavior here is. Should we fire onerror here?
Blocks: b2g-notifications
Flags: needinfo?(annevk)
Comment 3•11 years ago
|
||
What is logcat? Can someone describe the steps to reproduce in terms of the Notifications API?
The close() method simply becomes a no-op so you can race it.
Flags: needinfo?(annevk)
Comment 4•11 years ago
|
||
Ok - I think you answered my question. No-op, but no onerror callback. Will fix the test case here then.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: in-moztrap?(jsmith)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•