Closed Bug 1395525 Opened 4 years ago Closed 4 years ago
Make sure Tailing preffed off makes the browser behave the same way as before the feature has landed
According WPT testing and also some talos results, few of the changes I've add as part of bug 1358060 that are not covered by preferences may cause regressions or simply make the browser schedule the resource satisfaction a slightly different way. This bug is to make sure those changes are covered (killable) by the "network.http.tailing.enabled" preference.
- adds nsContentUtils::IsTailingEnabled() pref shortcut for convenience - all parts that have changed are now covered by the main preference, switching it off should make the browser behave exactly the same as before
Attachment #8903138 - Flags: review?(dd.mozilla)
Attachment #8903138 - Flags: review?(dd.mozilla) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/e4fcf1fd4e54 Make all changes landed as part of tracker request tailing preferrable. r=dragana
You need to log in before you can comment on or make changes to this bug.