Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(508)

Unified Diff: third_party/WebKit/Source/core/frame/Settings.json5

Issue 2753863003: Clarify Beacon transmission limit checking. (Closed)
Patch Set: rebased upto r459528 Created 3 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/Source/core/frame/Settings.json5
diff --git a/third_party/WebKit/Source/core/frame/Settings.json5 b/third_party/WebKit/Source/core/frame/Settings.json5
index ea068413118ea7333091fdc472e808b02d2e6322..56a835b542c3a7b571860d22645143d47c3d9d45 100644
--- a/third_party/WebKit/Source/core/frame/Settings.json5
+++ b/third_party/WebKit/Source/core/frame/Settings.json5
@@ -611,7 +611,8 @@
// smaller payloads transmitted as a page is unloading, not a general (one-way)
// network transmission API. The spec <https://w3c.github.io/beacon/> does not
// proscribe an upper limit, but allows for it -- the underlying API will return
- // 'false' in that case.
+ // 'false' in that case. If the value is set to a negative value, no limit
+ // will be imposed.
{
name: "maxBeaconTransmission",
initial: 65536,

Powered by Google App Engine
This is Rietveld 408576698