33f8dca276863d1cbc33511d47ba198f820400ea: Bug 1544228 - Fix some about: pages text color contrast for GTK dark system themes r=dao
Kestrel <ke5trel@protonmail.com> - Thu, 23 May 2019 10:44:29 +0000 - rev 475179
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1544228 - Fix some about: pages text color contrast for GTK dark system themes r=dao Some about: pages use -moz-Dialog background color which is dark with popular GTK dark themes (Adwaita-dark, Yaru-dark) so the text color needs to be set to -moz-DialogText to retain contrast. This affects about:buildconfig, about:cache, about:serviceworkers and about:credits. Differential Revision: https://phabricator.services.mozilla.com/D31414
b09e197ba5a3213026316668e89707749d5f3821: Bug 1550956: Import builtins in Python 3 compatible way r=firefox-build-system-reviewers,chmanchester
Kagami Sascha Rosylight <saschanaz@outlook.com> - Thu, 23 May 2019 03:57:17 +0000 - rev 475178
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1550956: Import builtins in Python 3 compatible way r=firefox-build-system-reviewers,chmanchester Differential Revision: https://phabricator.services.mozilla.com/D30790
e882a5c576abc2c29ae3e3e3c5a27aefa0c2621e: Bug 1553022 - Don't use the given range in ScrollToWithOrigin in the case where scroll snap will happen. r=botond
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Thu, 23 May 2019 10:22:08 +0000 - rev 475177
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1553022 - Don't use the given range in ScrollToWithOrigin in the case where scroll snap will happen. r=botond ScrollToShowRect calls nsIScrollableFrame::ScrollTo with an nsRange which will be used to constrain the final scroll position so that if snapping needs to happen we need to ignore the given range not to constrain the final destination position in the range. Differential Revision: https://phabricator.services.mozilla.com/D31948
f68ba99112d6ee6bff3813714f869c87ebcf3143: Bug 1553022 - Stop descending down frame tree if we met another scrollable frame when we collect snap positions. r=botond
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Thu, 23 May 2019 10:27:31 +0000 - rev 475176
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1553022 - Stop descending down frame tree if we met another scrollable frame when we collect snap positions. r=botond From the last sentence of "3. Scroll Snap Model" [1] in the spec; Snap positions only affect the nearest ancestor scroll container on the element's containing block chain. [1] https://drafts.csswg.org/css-scroll-snap-1/#overview Differential Revision: https://phabricator.services.mozilla.com/D31947
97fd39fe7f582ff714a56a65194bf9ca01711686: Backed out 2 changesets (bug 1553022) for build bustage on builds/worker/workspace/build/src/layout/generic/nsGfxScrollFrame.cpp
Dorel Luca <dluca@mozilla.com> - Thu, 23 May 2019 13:08:25 +0300 - rev 475175
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Backed out 2 changesets (bug 1553022) for build bustage on builds/worker/workspace/build/src/layout/generic/nsGfxScrollFrame.cpp Backed out changeset d136380e4945 (bug 1553022) Backed out changeset 9a556ee9f039 (bug 1553022)
7cce412dd61b40d0ceda37ed32a64dda7d7b5e8d: Bug 1553491 - Renumber MarkColor to match intuition that 'black' is more marked than 'gray' r=sfink?
Jon Coppeard <jcoppeard@mozilla.com> - Wed, 22 May 2019 20:29:10 +0000 - rev 475174
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1553491 - Renumber MarkColor to match intuition that 'black' is more marked than 'gray' r=sfink? Differential Revision: https://phabricator.services.mozilla.com/D32160
7286e18fbc1775558b8653bb63576a47b31a5f3e: Bug 1553772 - Bug 1549812 - Try to assert a bit harder about stuff not flushing under our nose. r=TYLin,mats
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 23 May 2019 09:45:56 +0000 - rev 475173
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1553772 - Bug 1549812 - Try to assert a bit harder about stuff not flushing under our nose. r=TYLin,mats I think these should hold, everything that runs under them should just schedule other stuff to some later date: * Synth mouse events -> scheduled as refresh driver observers. * Scroll events -> Scheduled as well. * Caret state change events -> Also scheduled after last patch. * IME and accessibility stuff -> I don't think they can reenter layout. We can always revert this if it causes troubles, plus it shouldn't crash on release so should be fine. Differential Revision: https://phabricator.services.mozilla.com/D31090
58d40da713559f200d7ea651f2df0c434acee108: Bug 1553772 - Bug 1549812 - Don't run arbitrary script from AccessibleCaretManager callbacks. r=TYLin
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 23 May 2019 09:45:47 +0000 - rev 475172
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1553772 - Bug 1549812 - Don't run arbitrary script from AccessibleCaretManager callbacks. r=TYLin Instead, post the event for the next turn of the event loop. In this case, what killed the frame is ActionBarHandler.jsm via Selection.toString(). Depends on D31088 Differential Revision: https://phabricator.services.mozilla.com/D31089
32d724d2312caa420601b9cb7e3ef4bf1769b14e: Bug 1553772 - Bug 1549812 - fix testAccessibleCarets.js to account for more async event dispatching. r=TYLin
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 23 May 2019 09:47:00 +0000 - rev 475171
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1553772 - Bug 1549812 - fix testAccessibleCarets.js to account for more async event dispatching. r=TYLin Differential Revision: https://phabricator.services.mozilla.com/D32194
d136380e4945c8081a2952760143a0bb1e36df7c: Bug 1553022 - Don't use the given range in ScrollToWithOrigin in the case where scroll snap will happen. r=botond
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Thu, 23 May 2019 09:44:26 +0000 - rev 475170
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1553022 - Don't use the given range in ScrollToWithOrigin in the case where scroll snap will happen. r=botond ScrollToShowRect calls nsIScrollableFrame::ScrollTo with an nsRange which will be used to constrain the final scroll position so that if snapping needs to happen we need to ignore the given range not to constrain the final destination position in the range. Differential Revision: https://phabricator.services.mozilla.com/D31948
9a556ee9f0398585c6fdf2fe7193907de92e247e: Bug 1553022 - Stop descending down frame tree if we met another scrollable frame when we collect snap positions. r=botond
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Thu, 23 May 2019 09:44:58 +0000 - rev 475169
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1553022 - Stop descending down frame tree if we met another scrollable frame when we collect snap positions. r=botond From the last sentence of "3. Scroll Snap Model" [1] in the spec; Snap positions only affect the nearest ancestor scroll container on the element's containing block chain. [1] https://drafts.csswg.org/css-scroll-snap-1/#overview Differential Revision: https://phabricator.services.mozilla.com/D31947
c2327979957d727efdea1d7f87d9f044aace1da8: Bug 1549812 - ScrollFrameRectIntoView should handle the frame going away. r=mats
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 17 May 2019 16:33:26 +0000 - rev 475168
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1549812 - ScrollFrameRectIntoView should handle the frame going away. r=mats ScrollToShowRect already considers that possibility, so not doing it on the caller is a bug. Ideally scroll observers shouldn't be able to run script, more to that in a second. Differential Revision: https://phabricator.services.mozilla.com/D31088
f33e3b5366fc340d078488ab37bef6ed639fdd1e: Bug 1553145 - Improve Remote Settings documentation r=glasserc
Mathieu Leplatre <mathieu@mozilla.com> - Thu, 23 May 2019 09:19:37 +0000 - rev 475167
Push 36057 by aciure@mozilla.com at Thu, 23 May 2019 21:52:03 +0000
Bug 1553145 - Improve Remote Settings documentation r=glasserc Differential Revision: https://phabricator.services.mozilla.com/D32130
9a89e2b0fa9d7e6393deb47452e3954d4c5adf66: Bug 1553957 - Include WindowProxyHolder.h in EventTarget.h. r=smaug a=Aryx
Jorg K <jorgk@jorgk.com> - Thu, 23 May 2019 23:09:19 +0200 - rev 475166
Push 36056 by mozilla@jorgk.com at Thu, 23 May 2019 21:36:12 +0000
Bug 1553957 - Include WindowProxyHolder.h in EventTarget.h. r=smaug a=Aryx
5a63f841eacb1632a595c30bfb3d81636a2cde8d: Merge mozilla-inbound to mozilla-central. a=merge
Daniel Varga <dvarga@mozilla.com> - Thu, 23 May 2019 18:54:21 +0300 - rev 475165
Push 36055 by dvarga@mozilla.com at Thu, 23 May 2019 15:55:11 +0000
Merge mozilla-inbound to mozilla-central. a=merge
32efcd22ed9c27d664699b8d8f22f8da92857b07: Bug 1543458 - Make the JS subscript loader compile UTF-8 directly without inflating it. r=arai
Jeff Walden <jwalden@mit.edu> - Wed, 10 Apr 2019 10:48:50 -0700 - rev 475164
Push 36055 by dvarga@mozilla.com at Thu, 23 May 2019 15:55:11 +0000
Bug 1543458 - Make the JS subscript loader compile UTF-8 directly without inflating it. r=arai Differential Revision: https://phabricator.services.mozilla.com/D26959
f20b97afe8189f9e8d44d834c9976439be05e08a: Bug 1543458 - Make the JS component loader compile UTF-8 directly without inflating it. r=arai
Jeff Walden <jwalden@mit.edu> - Wed, 10 Apr 2019 10:44:58 -0700 - rev 475163
Push 36055 by dvarga@mozilla.com at Thu, 23 May 2019 15:55:11 +0000
Bug 1543458 - Make the JS component loader compile UTF-8 directly without inflating it. r=arai Differential Revision: https://phabricator.services.mozilla.com/D26958
29bf13f9b35adc3ee9952d127af84a9ba1adc95a: Bug 1540401 - Backout Part 2: Convert MOZ_DIAGNOSTIC_ASSERT back to MOZ_ASSERT since bug 1541775 hasn't been fixed yet; r=asuth
Jan Varga <jan.varga@gmail.com> - Thu, 23 May 2019 10:26:20 +0200 - rev 475162
Push 36055 by dvarga@mozilla.com at Thu, 23 May 2019 15:55:11 +0000
Bug 1540401 - Backout Part 2: Convert MOZ_DIAGNOSTIC_ASSERT back to MOZ_ASSERT since bug 1541775 hasn't been fixed yet; r=asuth
490fd8b22deae669be2ee735757b0c8d5e417406: Merge mozilla-central to mozilla-inbound. a=merge CLOSED TREE
Bogdan Tara <btara@mozilla.com> - Thu, 23 May 2019 07:44:57 +0300 - rev 475161
Push 36055 by dvarga@mozilla.com at Thu, 23 May 2019 15:55:11 +0000
Merge mozilla-central to mozilla-inbound. a=merge CLOSED TREE
d4a9b4dd03ca5c3db2bd10e8097d9817435ba37d: Bug 1525720, part 17 - Ignore nsIRemoteTab methods after we have destroyed the browser. r=nika
Ryan Hunt <rhunt@eqrion.net> - Wed, 15 May 2019 12:34:14 -0500 - rev 475160
Push 36055 by dvarga@mozilla.com at Thu, 23 May 2019 15:55:11 +0000
Bug 1525720, part 17 - Ignore nsIRemoteTab methods after we have destroyed the browser. r=nika It's possible for front-end references to nsIRemoteTab to outlive the IPDL actor. When this happens, we should ignore methods and property accesses. The one special case is that some code expects to be able to access the TabId after the browser has been destroyed. For this we can just cache the ID. Differential Revision: https://phabricator.services.mozilla.com/D31449
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip