a918bec3a72ae393aef08d2b29c5a54bb55b468c: Bug 1307881 - Part 3 - Remove unused filteredMessageVisible prop from the state;r=nchevobbe
Brian Grinstead <bgrinstead@mozilla.com> - Thu, 31 Aug 2017 21:45:00 -0700 - rev 378161
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1307881 - Part 3 - Remove unused filteredMessageVisible prop from the state;r=nchevobbe MozReview-Commit-ID: D5TKjuuvpgt
27d26ef5a86c7927df0ba3fde7bbe0258f36998f: Bug 1307881 - Part 2 - Provide a UI within the Web Console for managing persistence;r=nchevobbe
Brian Grinstead <bgrinstead@mozilla.com> - Thu, 31 Aug 2017 21:43:42 -0700 - rev 378160
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1307881 - Part 2 - Provide a UI within the Web Console for managing persistence;r=nchevobbe MozReview-Commit-ID: GVkOms1o74c
a8bbf4e5c665e3ae8085e8ad9e5104b13bc4f0ec: Bug 1307881 - Part 1 - Split message persistence prefs into two, one for the netmonitor and one for the console;r=Honza
Brian Grinstead <bgrinstead@mozilla.com> - Thu, 31 Aug 2017 21:42:15 -0700 - rev 378159
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1307881 - Part 1 - Split message persistence prefs into two, one for the netmonitor and one for the console;r=Honza MozReview-Commit-ID: 4i8heIyPEv0
fe4bf0764f4df2ae2186648a6d49a78279730296: Bug 1394935 - A crash test. r=bholley
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Fri, 01 Sep 2017 13:27:11 +0900 - rev 378158
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1394935 - A crash test. r=bholley MozReview-Commit-ID: 1zSJPx2sVbi
78eebfdf0ec211b5a2f47c2cab8dba1b1207d17c: servo: Merge #18322 - Update WR (font instance API) (from glennw:update-wr-fonts-2); r=emilio
Glenn Watson <github@intuitionlibrary.com> - Thu, 31 Aug 2017 21:59:30 -0500 - rev 378157
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
servo: Merge #18322 - Update WR (font instance API) (from glennw:update-wr-fonts-2); r=emilio WR now has a concept of font templates and font instances. This makes the WR font interfaces closer to Cairo and Gecko, and also makes some future performance optimizations possible. A font template is the font family, and data backing the font. A font instance is a reference to a font template and per-instance options, such as font size, anti-aliasing settings etc. To update Servo in a minimally invasive way, I added a new font cache call, that creates a font instance. This means that when a font is created, and doesn't exist in the cache there are now two calls to the font cache thread. We could refactor the font cache to make this work in one call, which we should do in the future. However, refactoring the font cache is a large chunk of work by itself. The extra call is only when a font doesn't already exist in the font context cache, so it should have minimal performance impact. Source-Repo: https://github.com/servo/servo Source-Revision: f7d238d1f38e4d6798cf2f18d72e61b3dd35bd2c
b7a2fb849cfa6e12d5e43b8af3cee6eca97854d5: Bug 1394304 - Use pref to control whether to open url bar results in a new tab. r=adw
Ting-Yu Lin <tlin@mozilla.com> - Mon, 28 Aug 2017 13:31:20 +0800 - rev 378156
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1394304 - Use pref to control whether to open url bar results in a new tab. r=adw MozReview-Commit-ID: 9cIttOqOU4d
14960c3fbf80f4f366b7224792c65089e6192a69: Bug 1392888 - [Form Autofill] Avoid using getElementsByTagName. r=MattN
Luke Chang <lchang@mozilla.com> - Thu, 24 Aug 2017 10:40:48 +0800 - rev 378155
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1392888 - [Form Autofill] Avoid using getElementsByTagName. r=MattN MozReview-Commit-ID: 7Km6xkR4ffq
628a46720153fefa077044bff627d2f8f5b5cc17: Backed out 6 changesets (bug 1302470) for mochitest-chrome failures
Phil Ringnalda <philringnalda@gmail.com> - Thu, 31 Aug 2017 20:04:24 -0700 - rev 378154
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Backed out 6 changesets (bug 1302470) for mochitest-chrome failures CLOSED TREE Backed out changeset 3aab8b1494ef (bug 1302470) Backed out changeset fdd40abac611 (bug 1302470) Backed out changeset a67bc2f1b624 (bug 1302470) Backed out changeset 160522290018 (bug 1302470) Backed out changeset 6b948c533944 (bug 1302470) Backed out changeset 399011313b3c (bug 1302470) MozReview-Commit-ID: 2B3uMAkzNGv
85e0bc442b6188e1f706f7681c7a586919053294: Backed out 4 changesets (bug 1394883) for Windows signing chain-of-trust failures
Phil Ringnalda <philringnalda@gmail.com> - Thu, 31 Aug 2017 20:02:34 -0700 - rev 378153
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Backed out 4 changesets (bug 1394883) for Windows signing chain-of-trust failures CLOSED TREE Backed out changeset e3f42eca51c1 (bug 1394883) Backed out changeset 081f830cf285 (bug 1394883) Backed out changeset 9426705a05af (bug 1394883) Backed out changeset 3a579a5054ef (bug 1394883) MozReview-Commit-ID: 2viO8A8arHd
bd25a5e1a355a31efcdb63b3c5954746fdfb7dec: Bug 1375635 - Add telemetry for how often and long users are in bad authentication states. r=Dexter,rweiss+418169,tcsc
Mark Hammond <mhammond@skippinet.com.au> - Thu, 27 Jul 2017 11:59:24 +1000 - rev 378152
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1375635 - Add telemetry for how often and long users are in bad authentication states. r=Dexter,rweiss+418169,tcsc MozReview-Commit-ID: BW8ixM3wmxJ
de726c1fbb1e85aad4ed2f3f3d91366024818739: servo: Merge #18317 - Enable Custom Elements by Default (from cbrewster:custom_elements_enable); r=jdm
Connor Brewster <connor.brewster@eagles.oc.edu> - Thu, 31 Aug 2017 19:57:29 -0500 - rev 378151
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
servo: Merge #18317 - Enable Custom Elements by Default (from cbrewster:custom_elements_enable); r=jdm <!-- Please describe your changes on the following line: --> --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [X] These changes fix #9372 (github issue number if applicable). <!-- Either: --> - [ ] There are tests for these changes OR - [X] These changes do not require tests because enabling pref flag. <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> Source-Repo: https://github.com/servo/servo Source-Revision: e10e56930fa8733e47f0a201aa5a80a5dc7c2d10
aa111604eaa34be601b91b32aa077939b4252c28: Bug 1395439 - Clean out useless flags to reuse cache FillGeometry in nsSVGUtils::GetBBox. r=longsonr+218550
cku <cku@mozilla.com> - Thu, 31 Aug 2017 12:21:39 +0800 - rev 378150
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1395439 - Clean out useless flags to reuse cache FillGeometry in nsSVGUtils::GetBBox. r=longsonr+218550 In nsSVGUtils::GetBBox, we cache fill-gemorty's bbox in ObjectBoundingBoxProperty of the given frame[1] so that we can just return the cache value without recomputing bbox. Some new added flags, such as eUseFrameBoundsForOuterSVG, prevent storing and reusing this cache value. This patch is trying to make this cache mechanism work again. [1] https://hg.mozilla.org/mozilla-central/file/ef585ac7c476/layout/svg/nsSVGUtils.cpp#l1119 MozReview-Commit-ID: 8vWDzFi8qCw
b18cad4e3274cb2a6b92eb95779f099b79c4fd5d: Bug 1395703 - Make sure modifiedBySync CV field isn't passed to ContentProvider on updates r=rnewman
Grigory Kruglov <gkruglov@mozilla.com> - Thu, 31 Aug 2017 18:05:20 -0400 - rev 378149
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1395703 - Make sure modifiedBySync CV field isn't passed to ContentProvider on updates r=rnewman Comment from bugzilla on this ugly hack: While processing bookmarks, we sometimes need to mark them for re-upload as we're inserting new ones or updating existing ones. For example, we might set or update a dateAdded field. We perform insertions "in-bulk", and so we might be inserting some bookmarks which need to be re-uploaded, and some bookmarks which don't. We compile an array of ContentValue objects, and make a single call to our ContentProvider. This means we can't use a URI param to indicate our intent, and so a non-column field in ContentValues objects - modifiedFromSync - is set for those bookmarks which need special treatment during insertion. Bug 1392802 added a similar mechanism for updating bookmarks. However, updates are done differently - currently, we perform a single call to our ContentProvider for each bookmark. Which means we _can_ use a URI field as a signaling mechanism, which is what that patch did. However, in haste I forgot to take into consideration existing signaling mechanism, which lead to update failures. And so we're left with an even clumsier interface to our data store, with two ways to signal the same thing in different circumstances... A quick solution is to just make sure 'modifiedBySync' field never makes its way to contentprovider on updates; a more refined fix would probably modify update logic to use a ContentValues field for consistency... Either way, there's going to be something ugly, somewhere in the code. I anticipate a lot of this code changing sometime soon in order to support better transactionality of bookmark syncing, and smarter merging, and so I'm inclined to just to the simple thing for now. MozReview-Commit-ID: H10LFsqjbFY
001d66bec22f15c253e21306c72d04b518b94dd0: Bug 1395762 - Update Stylo check in file_restyling_xhr_doc.html. r=birtles
J. Ryan Stinnett <jryans@gmail.com> - Thu, 31 Aug 2017 18:57:25 -0500 - rev 378148
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1395762 - Update Stylo check in file_restyling_xhr_doc.html. r=birtles Automation also uses env vars to change the Stylo mode, so reading the pref is not enough. Change the test to `isStyledByServo` which covers all cases. MozReview-Commit-ID: KLh42b4roF4
b28fb20723996f86bdf9c1e9e53839f82ca5c353: Bug 1383898 - Add tablet icon to Send Page to Device panel. r=markh
Edouard Oger <eoger@fastmail.com> - Tue, 29 Aug 2017 14:37:20 -0400 - rev 378147
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1383898 - Add tablet icon to Send Page to Device panel. r=markh MozReview-Commit-ID: SqxuO1g2J0
7e5fec0ca1ca960d24daece0c62aa5634f540222: Bug 1376507 - Handle a list of contexts instead of a single context. r=billm
Blake Kaplan <mrbkap@gmail.com> - Mon, 28 Aug 2017 16:05:11 -0700 - rev 378146
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1376507 - Handle a list of contexts instead of a single context. r=billm This might be prematurely optimized as it uses two lists (one list of active contexts and one list of inactive contexts) but I was really attracted by the idea of being able to answer questions like "is any context active" by only looking at a single context and not having to iterate the whole list every time we needed to do anything. It is really important that nobody touches any of the timestamps (or the mActive member) outside of the Watchdog lock. I thought about trying to encapsulate that data in its own class, but that felt like overkill. Let me know if you disagree. There are still a couple of uses of XPCJSContext::Get that probably need to be stamped out, but I think doing so will depend on the details of how we map JSContexts to XPCJSContext (and XPCJSRuntimes). I think that should wait for a separate bug. MozReview-Commit-ID: 9UZlh7Jutne
ded0b612dba768607ab11687d874b974a9855201: Bug 1376507 - Move state onto XPCJSContext. r=billm
Blake Kaplan <mrbkap@gmail.com> - Wed, 23 Aug 2017 17:40:09 -0700 - rev 378145
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1376507 - Move state onto XPCJSContext. r=billm The current code assumes it can store data about "the" XPCJSContext on the WatchdogManager singleton. Once we have more than one XPCJSContext running around, that won't be possible. This moves the needed data onto the XPCJSContext itself and gives the WatchdogManager the proper context to operate on. MozReview-Commit-ID: AxyFKp9LmH3
d4cea477b7e43db13c56656b6c24f4391538544c: Backed out 2 changesets (bug 1376507) for build bustage a=backout
Wes Kocher <wkocher@mozilla.com> - Thu, 31 Aug 2017 17:08:29 -0700 - rev 378144
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Backed out 2 changesets (bug 1376507) for build bustage a=backout Backed out changeset 266611b269cc (bug 1376507) Backed out changeset 04ecce0d1392 (bug 1376507) MozReview-Commit-ID: JC6tERhgDoS
d7cae06749f131a1fdffed1926fe526f7cfc89ee: Merge m-c to autoland, a=merge
Wes Kocher <wkocher@mozilla.com> - Thu, 31 Aug 2017 16:56:58 -0700 - rev 378143
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Merge m-c to autoland, a=merge MozReview-Commit-ID: BlE0HFQUP9c
266611b269cc876858346826d178a1e8fef0e0d4: Bug 1376507 - Handle a list of contexts instead of a single context. r=billm
Blake Kaplan <mrbkap@gmail.com> - Mon, 28 Aug 2017 16:05:11 -0700 - rev 378142
Push 94412 by archaeopteryx@coole-files.de at Fri, 01 Sep 2017 08:46:09 +0000
Bug 1376507 - Handle a list of contexts instead of a single context. r=billm This might be prematurely optimized as it uses two lists (one list of active contexts and one list of inactive contexts) but I was really attracted by the idea of being able to answer questions like "is any context active" by only looking at a single context and not having to iterate the whole list every time we needed to do anything. It is really important that nobody touches any of the timestamps (or the mActive member) outside of the Watchdog lock. I thought about trying to encapsulate that data in its own class, but that felt like overkill. Let me know if you disagree. There are still a couple of uses of XPCJSContext::Get that probably need to be stamped out, but I think doing so will depend on the details of how we map JSContexts to XPCJSContext (and XPCJSRuntimes). I think that should wait for a separate bug. MozReview-Commit-ID: 9UZlh7Jutne
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip