Automatic update from web-platform-tests
[Background Fetch] Add web platform tests for match.
Move existing match tests to a match file, and add a test for matching
with query options.
Change-Id: I678c968fb56c4ff5a715f29746ec1e3a81958a9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1535879
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643401}
--
wpt-commits: 80eca32f37872b8b6f146bd92c7a8759a990dae2
wpt-pr: 16020
Automatic update from web-platform-tests
[Background Fetch] Add web platform tests for match.
Move existing match tests to a match file, and add a test for matching
with query options.
Change-Id: I678c968fb56c4ff5a715f29746ec1e3a81958a9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1535879
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643401}
--
wpt-commits: 80eca32f37872b8b6f146bd92c7a8759a990dae2
wpt-pr: 16020
Automatic update from web-platform-tests
Remove two uses of dedicated-workers.idl (#14952)
Prerequisite for https://github.com/web-platform-tests/wpt/pull/12803.
--
wpt-commits: 45b6a5be22e5ea7596c55f5d1e65bae5e62e1656
wpt-pr: 14952
Automatic update from web-platform-tests
[Background Fetch] Fix flaky WP test that's timing out.
Due to the scheduler handling multiple requests, there is an issue where
the in-progress processed bytes are being overwritten.
This CL fixes the test by not relying on that value. The underlying
issue will be fixed in a follow-up CL.
Bug: 929929
Change-Id: I48a1d7bb3899c441cdbf8dd2c13623204c1b9213
Reviewed-on: https://chromium-review.googlesource.com/c/1460924
Reviewed-by: Mugdha Lakhani <nator@google.com>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630316}
--
wpt-commits: 7451c0c0cf527c8a91e56e539fad31f50356d494
wpt-pr: 15295
Automatic update from web-platform-tests
[Background Fetch] Display upload progress.
Use the progress updates from the DS, and make sure the registration
displays accurate information with regards to uploads.
Bug: 774054
Change-Id: Iccec2e61310442c051339505c2397bbaa244b50c
Reviewed-on: https://chromium-review.googlesource.com/c/1386865
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#618515}
--
wpt-commits: 9f99e81b2d827b50f5a97478a0d79a064cb99d5a
wpt-pr: 14622
Automatic update from web-platform-tests
[Background Fetch] Support access to active fetches.
This bug removes the check from renderer that prevents
this access, and updates idl files accordingly.
It also adds a WPT test to check that incomplete fetches
provide access to downloaded content for requests that
have completed.
Bug: 875201
Change-Id: Iffb477496a7c593ba8a5f9de1dbb21c6ae90f6f6
Reviewed-on: https://chromium-review.googlesource.com/c/1367725
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#618219}
--
wpt-commits: cfef55a1984f801494132ce5400f472b710ddf23
wpt-pr: 14416
Automatic update from web-platform-tests
[Background Fetch] Remove records_ from BackgroundFetchRegistration.
This had been introduced to simplify access to active fetches, but has
the following issues:
1. It makes match() and matchAll() inconsistent with Cache API's match()
and matchAll(), which return new independently-consumable response(s) every
time they're called.
2. It breaks retries for responses, when downloading from a server that
doesn't support resuming of downloads.
For details, see
https://docs.google.com/document/d/1CrbWrnnshhyp_SfiAeuODpnQX36GK3Bsi19rXQGez6Q/edit?usp=sharing
The CL also updates the WPT test accordingly.
Bug: 875201
Change-Id: I2c33717cbee36f0d707e814506c0bae9b5a4f31f
Reviewed-on: https://chromium-review.googlesource.com/c/1355121
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#613079}
--
wpt-commits: 073eaac34d507b0ab4c9e2bf0c0d85d9e39cdc2c
wpt-pr: 14298
Automatic update from web-platform-testsAdd a list of BackgroundFetchRecord objects to BackgroundFetchRegistration.
When we allow access to active background fetches, BackgroundFetchRecords for
the fetch can be accessed from multiple places. It simplifies matters if
we return the same record for a request whenever it's accessed.
This CL adds a (private) list of BackgroundFetchRecords to the
BackgroundFetchRegistration object, and updates it every time match and
matchAll() are called.
The second change introduced here is to not immediately resolve
responseReady() if the fetch is active and a response for the request
isn't yet available. Once the fetch has completed, or there's a response
available for the request, we resolve pending promises. We also make sure to
return the same promise (resolved or unresolved) for a given record,
every time responseReady is called.
For a more detailed discussion, see the following doc:
https://docs.google.com/document/d/1CrbWrnnshhyp_SfiAeuODpnQX36GK3Bsi19rXQGez6Q/edit?usp=sharing
Bug: 875201
Change-Id: I8cb386efd19086c0993ad2be2fb2691ad90597ec
Reviewed-on: https://chromium-review.googlesource.com/c/1336151
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#610410}
--
wpt-commits: 12720fdc8914deec3e7cc627036a26217cc1e908
wpt-pr: 14060
Automatic update from web-platform-testsAdd a list of BackgroundFetchRecord objects to BackgroundFetchRegistration.
When we allow access to active background fetches, BackgroundFetchRecords for
the fetch can be accessed from multiple places. It simplifies matters if
we return the same record for a request whenever it's accessed.
This CL adds a (private) list of BackgroundFetchRecords to the
BackgroundFetchRegistration object, and updates it every time match and
matchAll() are called.
The second change introduced here is to not immediately resolve
responseReady() if the fetch is active and a response for the request
isn't yet available. Once the fetch has completed, or there's a response
available for the request, we resolve pending promises. We also make sure to
return the same promise (resolved or unresolved) for a given record,
every time responseReady is called.
For a more detailed discussion, see the following doc:
https://docs.google.com/document/d/1CrbWrnnshhyp_SfiAeuODpnQX36GK3Bsi19rXQGez6Q/edit?usp=sharing
Bug: 875201
Change-Id: I8cb386efd19086c0993ad2be2fb2691ad90597ec
Reviewed-on: https://chromium-review.googlesource.com/c/1336151
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#610410}
--
wpt-commits: 12720fdc8914deec3e7cc627036a26217cc1e908
wpt-pr: 14060
Automatic update from web-platform-tests[Background Fetch] Fix match() crash.
Calling `match` was causing crashes in debug mode due to accessing
base::Optional<>::value without initialization. Calling match with
an unmatched request was crashing due to hitting a DCHECK. This returns
undefined now as per the spec.
Bug: 896768
Change-Id: I5d82e68ddca157a240ceaaec8990d2553366fbbb
Reviewed-on: https://chromium-review.googlesource.com/c/1289269
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#601541}
--
wpt-commits: aec4289d8db0aae98d4f171419ed1c8b60bc82d1
wpt-pr: 13603
Automatic update from web-platform-tests[Background Fetch] Throw DOMException for responseReady on abort.
According to the spec, responseReady in BackgroundFetchRecord should
throw an AbortError DOMException if the fetch was abandoned.
https://wicg.github.io/background-fetch/#create-record-objects (2.4.3)
Change-Id: Ieadf278acd061e05b8822014d0934f050fcac702
Reviewed-on: https://chromium-review.googlesource.com/c/1283692
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#600769}
--
wpt-commits: f3ca7fcb4507476c55812417b8d451c9ef33a380
wpt-pr: 13549
Automatic update from web-platform-tests[Background Fetch] Simplify fetch storage workflow.
In addition, MatchAll should return all records, including unprocessed
ones. To support this, the following changes were made:
- Creating a registration also stores all the requests with an empty
response in the cache.
- When an individual request is processed, the failure reason (if any)
is stored in the metadata.
- The logic of GetSettledFetchesTask was moved to
MarkRegistrationForDeletionTask. It checks the metadata rather than the
cache itself to find a failure reason (if any).
- Match/MatchAll logic was moved to a new database task
(MatchRequestsTask). A new API call was added to the cache storage to
allow querying request/response pairs. If a response is found to be
empty it will be exposed as a nullptr.
Change-Id: I631a3ef3da95117aed759a675fe591da5201eeca
Reviewed-on: https://chromium-review.googlesource.com/c/1280851
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#600768}
--
wpt-commits: b38f09e16029e5944ef273644ba52588977515b7
wpt-pr: 13528
Automatic update from web-platform-tests[Background Fetch] Add WPT tests for BackgroundFetchRegistration::abort
Re-resubmit cr/1261477
The issue was that there is a race condition between the abort going
through, and the downloaded file being persisted on disk. I added an
extra check in the WPT test.
Change-Id: I98aa005b4637c08f60a126a6c7c896c1c0edfddf
Reviewed-on: https://chromium-review.googlesource.com/c/1276557
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598848}
--
wpt-commits: c54a084daf22377e9c9ac3b50f9220ad0df27858
wpt-pr: 13473
Automatic update from web-platform-tests[Background Fetch] Notify observers of BackgroundFetchRegistration
of updates in failure_reason and result, everytime these change.
This CL also has the effect of sending the onprogress event
when failure_reason and result change upon completion of the
background fetch.
Change-Id: I137a73bbbddda56994b4914b677bec9cc7183993
Reviewed-on: https://chromium-review.googlesource.com/c/1264589
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598839}
--
wpt-commits: 2ada2e794af8672b3988f8b9f085301207e5f78d
wpt-pr: 13398
Automatic update from web-platform-tests[Background Fetch] Add WPT tests for BackgroundFetchRegistration::abort
Re-resubmit cr/1261477
The issue was that there is a race condition between the abort going
through, and the downloaded file being persisted on disk. I added an
extra check in the WPT test.
Change-Id: I98aa005b4637c08f60a126a6c7c896c1c0edfddf
Reviewed-on: https://chromium-review.googlesource.com/c/1276557
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598848}
--
wpt-commits: c54a084daf22377e9c9ac3b50f9220ad0df27858
wpt-pr: 13473
Automatic update from web-platform-tests[Background Fetch] Notify observers of BackgroundFetchRegistration
of updates in failure_reason and result, everytime these change.
This CL also has the effect of sending the onprogress event
when failure_reason and result change upon completion of the
background fetch.
Change-Id: I137a73bbbddda56994b4914b677bec9cc7183993
Reviewed-on: https://chromium-review.googlesource.com/c/1264589
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598839}
--
wpt-commits: 2ada2e794af8672b3988f8b9f085301207e5f78d
wpt-pr: 13398
Automatic update from web-platform-testsRevert "Resubmit cr/1261477"
This reverts commit e2d1946acc8a4c2e0651958d663ef04c3eefe202.
Reason for revert: FindIt identified it as a source of flakiness in crbug/893511
Bug: 893511
Original change's description:
> Resubmit cr/1261477
>
> I reproduced the failure locally, and then re-ran with the changes 100
> time successfully
>
> TBR=peter@chromium.org
>
> Change-Id: Ieb60211fcd9c6beb1aec2b152f298335c4d9178b
> Reviewed-on: https://chromium-review.googlesource.com/c/1264640
> Reviewed-by: Mugdha Lakhani <nator@chromium.org>
> Commit-Queue: Rayan Kanso <rayankans@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#597106}
TBR=nator@chromium.org,rayankans@chromium.org
# Not skipping CQ checks because original CL landed > 1 day ago.
Change-Id: I8e0d0d5339f3f2ea8106dc76bf5bf7d4b8f0d243
Reviewed-on: https://chromium-review.googlesource.com/c/1270736
Reviewed-by: Olga Sharonova <olka@chromium.org>
Commit-Queue: Olga Sharonova <olka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#597883}
--
wpt-commits: 63ef84e18161b7ce0f11d166553f090913d4d1c3
wpt-pr: 13431
Automatic update from web-platform-testsResubmit cr/1261477
I reproduced the failure locally, and then re-ran with the changes 100
time successfully
TBR=peter@chromium.org
Change-Id: Ieb60211fcd9c6beb1aec2b152f298335c4d9178b
Reviewed-on: https://chromium-review.googlesource.com/c/1264640
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#597106}
--
wpt-commits: 786e201985b7c46ef59185c2c519f9081374fb2a
wpt-pr: 13390
Automatic update from web-platform-tests[Background Fetch] Add WPT tests for BackgroundFetchRegistration::abort
Simplify event dispatching code, and also allow for match/matchAll to be
called with the abort event.
Change-Id: I3a9d17102f176f7c68131ea144e555a44ffd6ab1
Reviewed-on: https://chromium-review.googlesource.com/c/1261477
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596723}
--
wpt-commits: 23cc12436af526289e615bf66171537ed11598fd
wpt-pr: 13360
Automatic update from web-platform-tests[Background Fetch] Set bad-status as failureReason
when one of the settled fetches has a response with a bad status.
Bug: 876691
Change-Id: I45af6b792a6a43e5b091bc5fe6f40d011bdabac5
Reviewed-on: https://chromium-review.googlesource.com/1233693
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592836}
--
wpt-commits: 9dd846c1243e6a5631a8ddfc1b885cc14561ae0a
wpt-pr: 13079
Automatic update from web-platform-tests[Background Fetch] Miscellaneous cleanups.
1. A check for state needs to be removed from a WPT test, since we've removed this
attribute from the BackgroundFetchRegistration object.
2. Update calls in matchImpl() from resolver->Reject to ScriptState::RejectWithDOMException.
Change-Id: Ie979ad3675ac7d093ae908604e683802db8115a0
Reviewed-on: https://chromium-review.googlesource.com/1230713
Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592050}
--
wpt-commits: 8abd5d0c3f43ebd83c533e6ac096686879183bd8
wpt-pr: 13051
Automatic update from web-platform-tests[Background Fetch] Remove dangling markup test
from the WPT suite.
This was added in response to an ongoing CL in the Fetch spec,
which nobody is championing at present and isn't part of the spec.
Here's the proposed spec change for reference:
https://github.com/whatwg/fetch/pull/519/commits
Bug: 884708
Change-Id: I185a876147ab7e02edd611840a237dce1cab750a
Reviewed-on: https://chromium-review.googlesource.com/1228060
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592023}
--
wpt-commits: faff61888337ce764d0170a81218d13ae53f5cfb
wpt-pr: 13036
Automatic update from web-platform-tests[Background Fetch] Implement recordsAvailable.
This has been added to the spec recently:
https://wicg.github.io/background-fetch/#dom-backgroundfetchregistration-recordsavailable
and lets the developer know whether the associated with the fetch are
still accessible.
I've simplified BackgroundFetchContext::CleanupRegistration() and added some
tests.
Bug: 881885
Change-Id: I7e12002ffd304727f7e538392879a382eed67fa4
Reviewed-on: https://chromium-review.googlesource.com/1216066
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591660}
--
wpt-commits: 445544dcf920e46d158bfe82b1e45e30360ed278
wpt-pr: 12963
Automatic update from web-platform-tests[Background Fetch] Reject when requests have body.
With this CL,
1. Record the BackgroundFetch.HasRequestsWithBody UMA metric, which is
true if any requests in the background fetch contain a body, false otherwise.
2. Reject the fetch() promise, if any requests do contain a body.
Bug: 881344
Change-Id: I595800adefe1dcc2c8bb04bec2295cc2886d963d
Reviewed-on: https://chromium-review.googlesource.com/1210125
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590309}
--
wpt-commits: b02f81005983ebcce822f1cc9a398fe38cad4ea1
wpt-pr: 12873
--HG--
extra : rebase_source : 401487c3dbefba9b07ed4109164b2916772b68ca
extra : source : 1e41acd18239f1a4d20b9dbb9a643e7928a93400
Automatic update from web-platform-tests[Background Fetch] Reject when requests have body.
With this CL,
1. Record the BackgroundFetch.HasRequestsWithBody UMA metric, which is
true if any requests in the background fetch contain a body, false otherwise.
2. Reject the fetch() promise, if any requests do contain a body.
Bug: 881344
Change-Id: I595800adefe1dcc2c8bb04bec2295cc2886d963d
Reviewed-on: https://chromium-review.googlesource.com/1210125
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590309}
--
wpt-commits: b02f81005983ebcce822f1cc9a398fe38cad4ea1
wpt-pr: 12873
Automatic update from web-platform-tests[Background Fetch] Record via UMA whether a fetch has duplicate requests
Also reject the registration if that happens with a warning, and add a
failing WPT test.
Bug: 871174, 780025
Change-Id: Ibdcc49bc47ea959e0c255a48f5d090cb865a6e45
Reviewed-on: https://chromium-review.googlesource.com/1202262
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588614}
--
wpt-commits: 98c37ef258eb21fb1c3dbf508437e58be21c2145
wpt-pr: 12830
Automatic update from web-platform-tests[BackgroundFetch] Part 2: Implement BackgroundFetchFailureReason.
This is the second part, the plumbing on the blink side.
Bug: 876691, 869918
Change-Id: I62fe4aaf37f41b5ebd341ce4731f7fda1d486feb
Reviewed-on: https://chromium-review.googlesource.com/1185015
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#585906}
--
wpt-commits: e5fed3cb6962f0b6a76ee517a29b72febf2159de
wpt-pr: 12622
Automatic update from web-platform-tests[BackgroundFetch] Part 1: Remove BackgroundFetchSettledFetches.
This removes BackgroundFetchSettledFetches from blink, idl files,
and the WPT tests.
In a follow up CL I'll remove it from all the event dispatcher code
on the browser side.
This fix also makes cache_query_params optional in MatchRequests() in mojo.
This is required because otherwise the mojo bindings logic crashes the renderer
when we try to pass in a nullptr for cache_query_params from blink.
Bug: 869918, 863016
Change-Id: Ifa933451f98f82902d8455ba5401c629c8c24811
Reviewed-on: https://chromium-review.googlesource.com/1186735
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#585847}
--
wpt-commits: 0594f4ef03914ed61a07ef9bfa888633f4d510aa
wpt-pr: 12646
Automatic update from web-platform-tests[Background Fetch] Take remaining quota into account in Data Manager.
- Before registering the fetch make sure there is enough quota to
complete the fetch.
- Abandon the fetch if there is no quota to persist the response.
TBR=avi@chromium.org
Bug: 872735
Change-Id: I2a8348209989f85722e20bd8a5bccc75015fbf51
Reviewed-on: https://chromium-review.googlesource.com/1169202
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584099}
--
wpt-commits: 30c8b6dbce59669ba443dabb87ba49cedfd62e83
wpt-pr: 12546
Automatic update from web-platform-testsRe-enable the Background Fetch WPT tests
The flaky crashes should have been fixed now that the associated logic
has been removed from the scheduler.
https://chromium-review.googlesource.com/c/chromium/src/+/1165554
Bug: 869470, 869818
Change-Id: Ie077876289a28387e5f890e9a25abe5609857c14
Reviewed-on: https://chromium-review.googlesource.com/1170909
Commit-Queue: Peter Beverloo <peter@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583729}
--
wpt-commits: f4cfe41feec71829ec58aa0bf8ef3b8bf489dc7f
wpt-pr: 12533
Automatic update from web-platform-tests[Background Fetch] Idl changes, to align with the spec.
1. backgroundfetchclick and backgroundfetchabort are of type
BackgroundFetchEvent now.
2. BackgroundFetchEvent includes a BackgroundFetchRegistration object.
3. Temporarily (until match() and matchAll() have been implemented on
BackgroundFetchRegistration), BackgroundFetchUpdateUIEvent also includes a
BackgroundFetchSettledFetches object.
4. BackgroundFetchUpdateEvent --> BackgroundFetchUpdateUIEvent, and
inherits from BackgroundFetchEvent.
5. backgroundfetched --> backgroundfetchsuccess.
6. backgroundfetchsuccess and backgroundfetchfail are of type
BackgroundFetchUpdateUIEvent.
7. Update WPT tests accordingly.
Bug: 869918
Change-Id: Ibb05087e692b39c2dd34c990baeff642627b6520
Reviewed-on: https://chromium-review.googlesource.com/1158835
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582909}
--
wpt-commits: 39aac0cde328471b8a97b136c26a5293f55771b3
wpt-pr: 12328
Automatic update from web-platform-tests[Background Fetch] Reject BackgroundFetchUpdateEvent::UpdateUI if called again
Also add WPT that check
- calling updateUI works
- calling updateUI more than once throws an exception
Change-Id: I4b8e1847a09fd84a087d4f4af996ccf19c9f212b
Reviewed-on: https://chromium-review.googlesource.com/1159073
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582140}
--
wpt-commits: d6763dd2689061fb3dc5175852f56009fd3d1103
wpt-pr: 12263
