fc3d68852d40cbd616e0622f7265ce849374a0dd: Bug 1377689 - merge identical headers in set{Request,Response}Header, r=bz,mixedpuppy
Peter Snyder <psnyde2@uic.edu> - Mon, 04 Dec 2017 22:48:54 -0600 - rev 708960
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1377689 - merge identical headers in set{Request,Response}Header, r=bz,mixedpuppy MozReview-Commit-ID: Kpli9YzEvlt
699d482c86c9fab9ed2e5b51dd1369e6bee90a5c: Bug 1414853 - Ensure LayerManager's backend type is LAYERS_WR in CanUseAdvancedLayer since BasicCompositor might be used for remote extension process; r=sotaro
Kevin Chen <kechen@mozilla.com> - Tue, 05 Dec 2017 16:49:14 +0800 - rev 708959
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1414853 - Ensure LayerManager's backend type is LAYERS_WR in CanUseAdvancedLayer since BasicCompositor might be used for remote extension process; r=sotaro MozReview-Commit-ID: KzAUXKWJf58
6b8a627984d8e475fb3f24421f6edd9a7d41b5a8: Bug 1415692 - Don't enforce runByManifest for `prefs` in manifests on disabled tests. r=ahal
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Tue, 05 Dec 2017 15:45:21 -0800 - rev 708958
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1415692 - Don't enforce runByManifest for `prefs` in manifests on disabled tests. r=ahal MozReview-Commit-ID: Fd9laiSVJwa
49358c06a1227b910c812d9a8bb007c3452ea7ed: Bug 1415692 - Show the bookmark toolbar in new profiles with > 3 bookmarks on it. r=Gijs,mak
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Mon, 04 Dec 2017 15:24:02 -0800 - rev 708957
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1415692 - Show the bookmark toolbar in new profiles with > 3 bookmarks on it. r=Gijs,mak MozReview-Commit-ID: C3tmqIrt5ak
5d1f0d1c29a44e4d148cb32a19f91406f9bc808a: Bug 1423565 - Update tasks.json as per documentation. r=rillian
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 06 Dec 2017 14:59:35 +0100 - rev 708956
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1423565 - Update tasks.json as per documentation. r=rillian Most of the keywords used were deprecated and following versioning 0.1.0 even though it was marked as version 2.0.0. This also defines build-binaries as the default task, so that Command-Shift-B doesn't need any confirmation. MozReview-Commit-ID: UGDxqJYaFs
abc646522e7d59b7a96668582716b01fb7ef28e0: bug 1408416 - Remove inconsistent Telemetry strings from About dialogs r=Dexter
Chris H-C <chutten@mozilla.com> - Tue, 05 Dec 2017 11:05:53 -0500 - rev 708955
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
bug 1408416 - Remove inconsistent Telemetry strings from About dialogs r=Dexter On nightly and aurora we have supplemental strings about Telemetry in the About dialog/section. However, we already open the data policy tab (Desktop) and notification (Mobile) on nightly, aurora, -and beta- to more accurately tell users about our data policies. So let's remove the inconsistently-applied semi-hard-to-find strings. MozReview-Commit-ID: 3zjXQwi9r7v
454b93c818d35abd99f8ed80b317b5528e941f86: Bug 1416044 - Add telemetry probe for if userChrome.css is loaded. r=francois,jwatt
Sam Foster <sfoster@mozilla.com> - Tue, 28 Nov 2017 12:14:02 -0800 - rev 708954
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1416044 - Add telemetry probe for if userChrome.css is loaded. r=francois,jwatt * New USER_CHROME_CSS_LOADED histogram * Just log a boolean to reflect if the userChrome.css was successfully loaded at profile initialization, in the parent process. MozReview-Commit-ID: 8ffSNUot43I
8445570689af38fb7e6676d29a45f16228cc9d6c: Bug 1406675 - Allow storages in WebExtensions on customized cookieBehavior and lifetimePolicy prefs. r=asuth,aswan
Luca Greco <lgreco@mozilla.com> - Fri, 10 Nov 2017 00:49:33 +0100 - rev 708953
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1406675 - Allow storages in WebExtensions on customized cookieBehavior and lifetimePolicy prefs. r=asuth,aswan This commit ensures that WebExtension principals always get a nsICookieService::BEHAVIOR_ACCEPT cookieBehavior and a nsICookieService::ACCEPT_NORMALLY aLifetimePolicy: - the webextension pages are still able to use indexedDB and localStorage on a globally configured: "network.cookie.cookieBehavior = 2" ("Accept cookies from websites" unchecked in the about:preferences "use custom settings for history" section) - the webextension pages' localStorage does not switch in session-only mode on a globally configured: "network.cookie.lifetimePolicy = 2" ("Keep until I close Firefox" in the about:preferences "use custom settings for history" section) MozReview-Commit-ID: 5LOCvCgcokM
5fcb3d79de4abfb081b9aa255f7dc5fda8653cc9: Backed out 2 changesets (bug 1419336) for build bustage on Linux, OS X and mingw32 and failing modified devtools test browser_webconsole_network_messages_expand.js on Windows. r=backout on a CLOSED TREE
Sebastian Hengst <archaeopteryx@coole-files.de> - Wed, 06 Dec 2017 19:35:07 +0200 - rev 708952
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Backed out 2 changesets (bug 1419336) for build bustage on Linux, OS X and mingw32 and failing modified devtools test browser_webconsole_network_messages_expand.js on Windows. r=backout on a CLOSED TREE Backed out changeset 572bb0e72616 (bug 1419336) Backed out changeset 1cd28aa89b3e (bug 1419336)
c070c95edef7a728efc5ee9d852988762038bfed: Bug 1419825 - Callers of insertVisitedURIs may overwrite the history title passing a null title. r=kitcambridge
Marco Bonardo <mbonardo@mozilla.com> - Thu, 23 Nov 2017 18:44:07 +0100 - rev 708951
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1419825 - Callers of insertVisitedURIs may overwrite the history title passing a null title. r=kitcambridge MozReview-Commit-ID: EPU4mv8rn7h
1b587f4d7e816b5f4a1a69f6801724f709784e92: Bug 1415536 - Extend NotifyNetworkActivity to get sent/received bytes r=baku,valentin
Tarek Ziadé <tarek@mozilla.com> - Thu, 23 Nov 2017 09:37:54 +0100 - rev 708950
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1415536 - Extend NotifyNetworkActivity to get sent/received bytes r=baku,valentin MozReview-Commit-ID: Afdvz0lktY8
572bb0e726162c903bfb9e9c67226a43a7988eee: Bug 1419336 - Update tests; r=nchevobbe
Jan Odvarko <odvarko@gmail.com> - Wed, 06 Dec 2017 14:03:21 +0100 - rev 708949
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1419336 - Update tests; r=nchevobbe MozReview-Commit-ID: JLq8yY7hgEp
1cd28aa89b3e13a1d5a914434aa04c19c5a16539: Bug 1419336 - Properly update HTTPi UI if a request is opened before finish; r=nchevobbe
Jan Odvarko <odvarko@gmail.com> - Wed, 06 Dec 2017 11:42:37 +0100 - rev 708948
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1419336 - Properly update HTTPi UI if a request is opened before finish; r=nchevobbe MozReview-Commit-ID: GwkGlD1UB9G
3f061457c803c9f2c88d9018fed2fc414e857d25: Bug 1423594 Update functools import and pycompat r=rail
Simon Fraser <sfraser@mozilla.com> - Wed, 06 Dec 2017 14:56:56 +0000 - rev 708947
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1423594 Update functools import and pycompat r=rail MozReview-Commit-ID: GA6ArqyvJFU
78321e46393020c54dc8098f09f3a5412f79528d: Bug 1423539 Update funsize docker image and python3 r=rail
Simon Fraser <sfraser@mozilla.com> - Wed, 06 Dec 2017 12:00:50 +0000 - rev 708946
Push 92501 by dgottwald@mozilla.com at Thu, 07 Dec 2017 11:26:02 +0000
Bug 1423539 Update funsize docker image and python3 r=rail MozReview-Commit-ID: 2iWrYevwtvs
4f7cab53d07c864087f20ee8a9b12b93552aeadc: Bug 1423866 - Shutdown the vibrate thread when VR controllers are removed; r?kip draft
Daosheng Mu <daoshengmu@gmail.com> - Thu, 07 Dec 2017 19:20:49 +0800 - rev 708945
Push 92500 by bmo:dmu@mozilla.com at Thu, 07 Dec 2017 11:22:48 +0000
Bug 1423866 - Shutdown the vibrate thread when VR controllers are removed; r?kip MozReview-Commit-ID: IWvokDVH0x3
4436bc8de2c8a35aca84cfdf1566e04f4386c834: Bug 1386613 - stop using waitForMutations in aboutdebugging tests (remaining tests);r=ochameau draft
Julian Descottes <jdescottes@mozilla.com> - Tue, 05 Dec 2017 22:44:18 +0100 - rev 708944
Push 92499 by jdescottes@mozilla.com at Thu, 07 Dec 2017 11:15:02 +0000
Bug 1386613 - stop using waitForMutations in aboutdebugging tests (remaining tests);r=ochameau MozReview-Commit-ID: HDNzIFwp4Ur
42554ebf43c62e2ad7fb045c125c37a113a657c6: Bug 1423626 - Sanitize accent color to ignore alpha channel. r=jaws draft
Tim Nguyen <ntim.bugs@gmail.com> - Thu, 07 Dec 2017 11:12:49 +0000 - rev 708943
Push 92498 by bmo:ntim.bugs@gmail.com at Thu, 07 Dec 2017 11:13:20 +0000
Bug 1423626 - Sanitize accent color to ignore alpha channel. r=jaws MozReview-Commit-ID: AXQvUXkiLCW
467e960c4be1c17699aeb45816b051a687ce23a2: Bug 1399897 - restricted height for the console table, reimplemented the table with divs; r?nchevobbe draft
Towkir Ahmed <towkir17@gmail.com> - Thu, 07 Dec 2017 17:09:55 +0600 - rev 708942
Push 92497 by bmo:3ugzilla@gmail.com at Thu, 07 Dec 2017 11:11:38 +0000
Bug 1399897 - restricted height for the console table, reimplemented the table with divs; r?nchevobbe MozReview-Commit-ID: 8Ul2pmr84QJ
32e7d25e965361644597eb7c4972bc69ee1b48cd: Bug 1423840 - Rewrite the prefs parser. r=glandium,Manishearth draft
Nicholas Nethercote <nnethercote@mozilla.com> - Sun, 03 Dec 2017 00:26:36 +1100 - rev 708941
Push 92496 by nnethercote@mozilla.com at Thu, 07 Dec 2017 11:10:39 +0000
Bug 1423840 - Rewrite the prefs parser. r=glandium,Manishearth The prefs parser has two significant problems. - It doesn't separate tokenizing from parsing. - It is implemented as a loop around a big switch on a "current state" variable. As a result, it is hard to understand and modify, slower than it could be, and in obscure cases it fails to parse some valid input. This patch replaces it with a recursive descent parser (albeit one without any recursion!) that has separate tokenization. The new parser is easier to understand and modify, more correct, and has better error messages (including filenames). It also runs about 1.9x faster than the existing parser. (As measured by parsing greprefs.js's contents from memory 1000 times in succession, omitting the prefs hash table construction. If the table construction is included, it's about 1.6x faster.) The new parser is slightly stricter than the old parser in a few ways. - Disconcertingly, the old parser allowed arbitrary junk between prefs (including at the start and end of the prefs file) so long as that junk didn't include any of the following chars: '/', '#', 'u', 's', 'p'. I.e. a line like this: !foo@bar&pref("prefname", true); would be treated the same as this: pref("prefname", true); The new parser disallows such junk because it isn't necessary and seems like an unintentional botch by the old parser. - The old parser allowed character 0x1a (SUB) between tokens and treated it like '\n'. The new parser does not allow this character. SUB was used to indicate end-of-file (*not* end-of-line) in some old operating systems such as MS-DOS, but this doesn't seem necessary today. - The old parser tolerated (with a warning) invalid escape sequences within string literals -- such as "\q" (not a valid escape) and "\x1" and "\u12" (both of which have insufficient hex digits) -- accepting them literally. The new parser does not tolerates invalid escape sequences because it doesn't seem necessary and would complicate things. - The old parser tolerated character 0x00 (NUL) within string literals; this is dangerous because C++ code that manipulates string values with embedded NULs will almost certainly consider those chars as end-of-string markers. The new parser treats NUL chars as end-of-file, to avoid this danger and because it facilitates a significant optimization (described within the code). - The old parser allowed integer literals to overflow, silently wrapping them. The new parser treats integer overflow as a parse error. This seems better, and it caught an existing overflow in testing/profiles/prefs_general.js, for places.database.lastMaintenance. The first of these changes meant that a couple of existing prefs with ";;" at the end had to be changed. The minor increase in strictness shouldn't be a problem for default pref files such as greprefs.js within the application (which we can modify), nor for app-written prefs files such as prefs.js. It could affect user-written prefs files such as user.js; the experience above suggests that ";;" is the most likely problem in practice. In my opinion, the risk here is acceptable. The new parser should also do a better job of tracking line numbers because it (a) treats "\r\n" sequences as a single end-of-line marker, and (a) pays attention to end-of-line sequences within string literals. The patch also adds a thorough test of valid syntax. (Note that the old parser fails to correctly parse this test in a few places because it misimplemented the grammar.) I'd like to also add tests for invalid syntax but the current design makes this challenging, because parse errors trigger an error message on the web console and a NS_ERROR_FILE_CORRUPTED return value from Parse(). MozReview-Commit-ID: 8EYWH7KxGG
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip