Closed
Bug 1229056
Opened 9 years ago
Closed 9 years ago
Implement ClientQueryOptions.includeUncontrolled
Categories
(Core :: DOM: Service Workers, defect)
Core
DOM: Service Workers
Tracking
()
RESOLVED
FIXED
mozilla45
Tracking | Status | |
---|---|---|
firefox45 | --- | fixed |
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
References
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
12.42 KB,
patch
|
jdm
:
review+
|
Details | Diff | Splinter Review |
This can be done relatively easily without needing bug 1032521 as a pre-requisite.
Updated•9 years ago
|
Keywords: dev-doc-needed
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8693719 -
Flags: review?(josh)
Comment 2•9 years ago
|
||
Comment on attachment 8693719 [details] [diff] [review]
Implement ClientQueryOptions.includeUncontrolled
Review of attachment 8693719 [details] [diff] [review]:
-----------------------------------------------------------------
::: testing/web-platform/mozilla/tests/service-workers/service-worker/clients-matchall-include-uncontrolled.https.html
@@ +47,5 @@
> + return info[0] == 'visible';
> + });
> + assert_equals(data.length, expected.length);
> + for (var i = 0; i < data.length; i++)
> + assert_array_equals(data[i], expected[i]);
There's no order defined by the spec, right? Can we make this less strict?
Attachment #8693719 -
Flags: review?(josh) → review+
Assignee | ||
Comment 3•9 years ago
|
||
(In reply to Josh Matthews [:jdm] from comment #2)
> Comment on attachment 8693719 [details] [diff] [review]
> Implement ClientQueryOptions.includeUncontrolled
>
> Review of attachment 8693719 [details] [diff] [review]:
> -----------------------------------------------------------------
>
> :::
> testing/web-platform/mozilla/tests/service-workers/service-worker/clients-
> matchall-include-uncontrolled.https.html
> @@ +47,5 @@
> > + return info[0] == 'visible';
> > + });
> > + assert_equals(data.length, expected.length);
> > + for (var i = 0; i < data.length; i++)
> > + assert_array_equals(data[i], expected[i]);
>
> There's no order defined by the spec, right? Can we make this less strict?
Correct.
The test sorts the array before comparison, so it doesn't depend on the order in which the implementation returns this stuff.
Comment 5•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox45:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
Comment 6•9 years ago
|
||
This is documented, see:
https://developer.mozilla.org/en-US/docs/Web/API/Clients/matchAll
A note has also been added to the relevant release notes:
https://developer.mozilla.org/en-US/Firefox/Releases/45#Service_Workers
Keywords: dev-doc-needed → dev-doc-complete
You need to log in
before you can comment on or make changes to this bug.
Description
•