582477c043dd5367a4acb02ca0b5032ad6d9997d: Bug 1511891 part 1 - Add BindVarOperation and use it for JSOP_BINDVAR in interpreter and JITs. r=tcampbell
Jan de Mooij <jdemooij@mozilla.com> - Fri, 11 Jan 2019 09:10:19 +0000 - rev 510558
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1511891 part 1 - Add BindVarOperation and use it for JSOP_BINDVAR in interpreter and JITs. r=tcampbell This also adds a GetVariablesObject helper so we don't have to duplicate the logic there. Differential Revision: https://phabricator.services.mozilla.com/D13698
fa4d4678a56854c7edf887747d25546d0f6929a9: Bug 1519367 - Update bug component for browser/base/content/test/sanitize/*. r=johannh
Mark Banner <standard8@mozilla.com> - Fri, 11 Jan 2019 12:10:41 +0000 - rev 510557
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1519367 - Update bug component for browser/base/content/test/sanitize/*. r=johannh Differential Revision: https://phabricator.services.mozilla.com/D16301
c8604d1a709caa37700cf712cbd4be848f62c6c0: Bug 1517074 - [Linux/Gtk] Enable native (xdg-desktop based) file dialog on KDE only due to Gtk+ regression, r=jhorak
Martin Stransky <stransky@redhat.com> - Fri, 11 Jan 2019 11:21:27 +0000 - rev 510556
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1517074 - [Linux/Gtk] Enable native (xdg-desktop based) file dialog on KDE only due to Gtk+ regression, r=jhorak Also add widget.allow-gtk-native-file-chooser preference value to force enable on all systems. Differential Revision: https://phabricator.services.mozilla.com/D16184
fc6fa6ebad8670134a9fca57ec7d7f1c9b60f4d1: Bug 1501709 - AudioWorkletGlobalScope::RegisterProcessor: check descriptors and convert them to an internal representation. r=karlt,baku,froydnj
Arnaud Bienner <arnaud.bienner@gmail.com> - Thu, 10 Jan 2019 18:45:38 +0000 - rev 510555
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1501709 - AudioWorkletGlobalScope::RegisterProcessor: check descriptors and convert them to an internal representation. r=karlt,baku,froydnj Differential Revision: https://phabricator.services.mozilla.com/D11741
9a22edb5c335044baf5fd63f28553d5f6cfb4103: Bug 1497002 - [Linux/CSD] Position headerbar button icons according to the actual button, r=jhorak
Martin Stransky <stransky@redhat.com> - Fri, 11 Jan 2019 11:24:06 +0000 - rev 510554
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1497002 - [Linux/CSD] Position headerbar button icons according to the actual button, r=jhorak Differential Revision: https://phabricator.services.mozilla.com/D16193
ebee32dc7abedd8621353f4ee27af9cf077e427e: Bug 1510790 - Introduce Redux selector for tracked changes to return the nested tree structure; r=pbro
Razvan Caliman <rcaliman@mozilla.com> - Fri, 11 Jan 2019 11:24:34 +0000 - rev 510553
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1510790 - Introduce Redux selector for tracked changes to return the nested tree structure; r=pbro This patch introduces a Redux selector for the Changes slice. A selector here is a fancy word for a method that returns a subset from the state without having to expose the state's structure to the consumer. It is also useful for returning a derived version of the state which we're using here. The tracked changed CSS rules in the Redux state are not stored in a nested structure. A shallow structure is easier to query and to work with in our use case. But the Changes panel needs to display CSS rules in a hierarchical structure (ex: a style rule which is a child of a @media rule). To do this, the React component used to build up the nested structure as it consumed the changes from the Redux state. To prevent rendering duplicates of rules (once as part of an ancestor's children and once as a standalone rule), the React component kept a reference of rules it had previously rendered. This had a flaw because it didn't account for the rule's stylesheet. The problem was that rules with identical selectors from different stylesheets would not all be rendered because they would be accidentally marked as previously rendered. This is too much knowledge of the business logic for the React component anyway. The Redux state should present itself in a way that's simple for the React component to consume. Hence the introduction of the `getChangesTree()` selector in this patch. This method allows us to present a comfortable structure to React while keeping the Redux structure comfortable for us to work with. This separation enables increased flexibility to restructure the Redux state without impacting the React components. More about Redux selectors here: https://redux.js.org/recipes/computing-derived-data Differential Revision: https://phabricator.services.mozilla.com/D16068
639afd87506132ba0a52b687c535a40791176787: Bug 1518590 - Change "More..." to "Advanced..." on advanced button. r=flod
Johann Hofmann <jhofmann@mozilla.com> - Fri, 11 Jan 2019 11:07:03 +0000 - rev 510552
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1518590 - Change "More..." to "Advanced..." on advanced button. r=flod Differential Revision: https://phabricator.services.mozilla.com/D16296
939479cc5903c7849098a9826fae052e2a5f5553: Bug 1519164 - Update content blocking UI tour url. r=nhnt11
Johann Hofmann <jhofmann@mozilla.com> - Fri, 11 Jan 2019 10:08:01 +0000 - rev 510551
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1519164 - Update content blocking UI tour url. r=nhnt11 Differential Revision: https://phabricator.services.mozilla.com/D16288
d084d6b3b5334c8bb3e96aaa1861276f0aa26095: Merge mozilla-central to autoland. a=merge on a CLOSED TREE
Razvan Maries <rmaries@mozilla.com> - Fri, 11 Jan 2019 11:36:24 +0200 - rev 510550
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Merge mozilla-central to autoland. a=merge on a CLOSED TREE
30fd54bb80897d6139d84e6c64937a6bc182f70d: Bug 1510574 - Remove shared memory segments from generated minidumps to cut down on the number of modules r=ted
Gabriele Svelto <gsvelto@mozilla.com> - Fri, 11 Jan 2019 08:56:07 +0000 - rev 510549
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1510574 - Remove shared memory segments from generated minidumps to cut down on the number of modules r=ted Differential Revision: https://phabricator.services.mozilla.com/D16188
c908cdfffe306ae3c461c54ae24c6c9882985592: Backed out 2 changesets (bug 1509575) for failing wpt at css/cssom-view/scroll-behavior-main-frame-root.html on a CLOSED TREE
Andreea Pavel <apavel@mozilla.com> - Fri, 11 Jan 2019 09:08:19 +0200 - rev 510548
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Backed out 2 changesets (bug 1509575) for failing wpt at css/cssom-view/scroll-behavior-main-frame-root.html on a CLOSED TREE Backed out changeset 245d6855cd3b (bug 1509575) Backed out changeset 7dcfa876f76c (bug 1509575)
65511e8d7a7e0df5df7c4b7c96ffc3cbd2590db3: Bug 1519281 - Remove leftovers from bug 1490765. r=nalexander
Mike Hommey <mh+mozilla@glandium.org> - Fri, 11 Jan 2019 05:02:07 +0000 - rev 510547
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1519281 - Remove leftovers from bug 1490765. r=nalexander Differential Revision: https://phabricator.services.mozilla.com/D16269
245d6855cd3bcb4ff5afd2ab9cc90ce2cedf8a00: Bug 1509575 - Restore the visual viewport offset from the main thread during a first paint. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 11 Jan 2019 04:21:29 +0000 - rev 510546
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1509575 - Restore the visual viewport offset from the main thread during a first paint. r=kats During a "first paint" transaction, compositor-side state such as APZ's copy of the visual viewport offset is overwritten. However, the scroll frame may persist on the main thread, and in such a case we want to restore the visual viewport offset stored in the scroll frame. This comes into play during e.g. navigation back to a page. Differential Revision: https://phabricator.services.mozilla.com/D16238
7dcfa876f76cd181cb7f8d482770c09b32f6a849: Bug 1509575 - Expose the isFirstPaint flag on LayerManager. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 11 Jan 2019 04:21:20 +0000 - rev 510545
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 1509575 - Expose the isFirstPaint flag on LayerManager. r=kats So that it's easily available during painting. The flag is set based on nsIPresShell::mIsFirstPaint, but the pres shell flag is cleared at the beginning of the paint, so we can't query it from the pres shell during the paint. Differential Revision: https://phabricator.services.mozilla.com/D16237
9afb01b30049bad89a837b6889da359df70a2a61: Merge mozilla-central to autoland. a=merge on a CLOSED TREE
Daniel Varga <dvarga@mozilla.com> - Fri, 11 Jan 2019 06:19:53 +0200 - rev 510544
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Merge mozilla-central to autoland. a=merge on a CLOSED TREE
897a97a4931de01e125e04a23a0139693c4ca163: Bug 181137 - part 9: Move kNSURIs in Document.cpp and FragmentOrElement.cpp into their users r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 11 Jan 2019 01:53:10 +0000 - rev 510543
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 181137 - part 9: Move kNSURIs in Document.cpp and FragmentOrElement.cpp into their users r=smaug Due to renaming nsContentIterator.cpp to ContentIterator.cpp, Document.cpp and FragmentOrElement.cpp are compiled in a unified cpp file now. However, both of them have same name constant, kNSURIs and some build systems claim that it in FragmentOrElement.cpp is never used. Fortunately, each of them is used only by one method. Therefore, this patch moves the each declaration into each user method. Differential Revision: https://phabricator.services.mozilla.com/D16186
dbf919528d9794a0570b6805a45e9baeac42629f: Bug 181137 - part 8: Make ContentIteratorBase and its subclasses non-refcountable r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 11 Jan 2019 01:52:26 +0000 - rev 510542
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 181137 - part 8: Make ContentIteratorBase and its subclasses non-refcountable r=smaug This patch makes ContentIteratorBase, PostContentIterator, PreContentIterator and ContentSubtreeIterator classes non-refcountable because most users can create their instances in stack and such users may be in a hot path. So, we can save a lot of cost of instantiation. Unfortunately, only ScriptableContentIterator creates one of the concrete classes and needs to destroy it properly. Therefore, its EnsureContentIterator(), destructor, traverse and unlink code becomes messy. However, ScriptableContentIterator was designed for automated tests and we need to maintain it not so many times. Therefore, improvement of other users must be worthwhiler than this demerit. Differential Revision: https://phabricator.services.mozilla.com/D15928
2a320da37ca0e1f47828e346f6b5e09ff2196ea8: Bug 181137 - part 7: Get rid of nsIContentIterator interface r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 11 Jan 2019 01:51:42 +0000 - rev 510541
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 181137 - part 7: Get rid of nsIContentIterator interface r=smaug Now, nobody requires nsIContentIterator interface. So, we can get rid of it. Unfortunately, there is no macro to keep the inherited class, ContentSubtreeIterator, in the cycle collection to make it keep managing ContentSubtreeIterator::mRange without nsISupports interface. Therefore, this patch moves it into ContentIteratorBase temporarily. Anyway, the following patch makes those classes not refcountable. At that time, this issue will be fixed. Differential Revision: https://phabricator.services.mozilla.com/D15927
61f2c3b1b36815443550ebb9378294c3b5a61ea8: Bug 181137 - part 6: Make nsFilteredContentIterator not derived from nsIContentIterator r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 11 Jan 2019 01:51:35 +0000 - rev 510540
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 181137 - part 6: Make nsFilteredContentIterator not derived from nsIContentIterator r=smaug nsFilteredContentIterator is used only by TextServicesDocument and there is no reason that it should be derived from nsIContentIterator except consistency. Additionally, it's now only class which is derived from nsIContentIterator except ContentIteratorBase. So, after this change, we can get rid of nsIContentIterator completely. This patch moves nsFilteredContentIterator into mozilla namespace and makes TextServicesDocument treat FilteredContentIterator directly instead of nsIContentIterator interface. Differential Revision: https://phabricator.services.mozilla.com/D15925
0d3c97c78d7ce2dc4a6790caa84b47b62d097b34: Bug 181137 - part 5: Make all users of PostContentIterator treat it directly rather than via nsIContentIterator r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 11 Jan 2019 01:50:19 +0000 - rev 510539
Push 10547 by ffxbld-merge at Mon, 21 Jan 2019 13:03:58 +0000
Bug 181137 - part 5: Make all users of PostContentIterator treat it directly rather than via nsIContentIterator r=smaug Now, all users of PostContentIterator can access it directly. This patch makes them use the concrete class directly. Differential Revision: https://phabricator.services.mozilla.com/D15923
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip