135af0c54dd7dda95f06eaf587b9d52fff5fa677: Bug 1455750 - Provide method for server to skip pausing. r=jimb
Jason Laster <jason.laster.11@gmail.com> - Tue, 22 May 2018 14:25:22 -0400 - rev 419787
Push 34049 by btara@mozilla.com at Fri, 25 May 2018 10:01:58 +0000
Bug 1455750 - Provide method for server to skip pausing. r=jimb
0f600a7141f24537c6c1284dbd6b11419ae51d3d: Merge autoland to mozilla-central. a=merge
Bogdan Tara <btara@mozilla.com> - Fri, 25 May 2018 12:59:02 +0300 - rev 419786
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Merge autoland to mozilla-central. a=merge
a3adfabc2b66a42aca290be4fd18bc77c86005eb: Bug 1463687 - Apply scrollbar style of root element to scrollbars of viewport. r=heycam
Xidorn Quan <me@upsuper.org> - Thu, 24 May 2018 16:34:58 +1000 - rev 419785
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1463687 - Apply scrollbar style of root element to scrollbars of viewport. r=heycam MozReview-Commit-ID: GWmhehtqO1U
de604a05f4172636e53dd3310d3aab658617e457: Bug 1456625 - Remove replacement XBL binding (Backout cb51f3bada90) r=Felipe
Timothy Guan-tin Chien <timdream@gmail.com> - Thu, 24 May 2018 18:23:48 +0800 - rev 419784
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1456625 - Remove replacement XBL binding (Backout cb51f3bada90) r=Felipe MozReview-Commit-ID: KlvjWWi3LkN
0f0e532db5ecc823a013c5f417d54694d6f38284: Bug 1464128 - Migrate bookmarks.html.in to LOCALIZED_GENERATED_FILES. r=ted.mielczarek
Nick Alexander <nalexander@mozilla.com> - Thu, 24 May 2018 11:28:47 -0700 - rev 419783
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1464128 - Migrate bookmarks.html.in to LOCALIZED_GENERATED_FILES. r=ted.mielczarek This one looks to be pretty straight-forward. It irritates me that the jar.mn entry doesn't explicitly say that the result is coming from the object directory, like locale/browser/bookmarks.html (!bookmarks.html) but that's for another day. MozReview-Commit-ID: Cw8E0VJhSxv
41590914f85ee74ee87bc0fa95752e7628311d5a: Bug 1463794: Move new WPT reftests to correct source-of-truth directory. r=dbaron+3881
Brad Werth <bwerth@mozilla.com> - Wed, 23 May 2018 12:53:34 -0700 - rev 419782
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1463794: Move new WPT reftests to correct source-of-truth directory. r=dbaron+3881 MozReview-Commit-ID: DcM0kVCAsZn
ce5992154d85188123ef7a32c10e4ae926697cc9: Bug 1463956 - allow Sync to remove all address and credit-card records. r=kitcambridge,MattN
Mark Hammond <mhammond@skippinet.com.au> - Thu, 24 May 2018 12:36:37 +1000 - rev 419781
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1463956 - allow Sync to remove all address and credit-card records. r=kitcambridge,MattN MozReview-Commit-ID: KSeJJfAGmRh
3a4017a4e792c04c1f1437dd12c61025e638e13a: Bug 1464181 - Enable mochitests on windows10-64-qr opt builds. r=jmaher
Kartikaya Gupta <kgupta@mozilla.com> - Thu, 24 May 2018 15:00:26 -0400 - rev 419780
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1464181 - Enable mochitests on windows10-64-qr opt builds. r=jmaher MozReview-Commit-ID: 5oerrEozVwd
7d10c4c82719fa1b820b9ae29cd878aecccd422a: Backed out 3 changesets (bug 1186265) for devtools chrome failures on browser_webconsole_visibility_messages.js. CLOSED TREE
Narcis Beleuzu <nbeleuzu@mozilla.com> - Fri, 25 May 2018 05:36:52 +0300 - rev 419779
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Backed out 3 changesets (bug 1186265) for devtools chrome failures on browser_webconsole_visibility_messages.js. CLOSED TREE Backed out changeset 4a9965aeeef3 (bug 1186265) Backed out changeset 55bd80764231 (bug 1186265) Backed out changeset 00fefd3eb634 (bug 1186265)
3f64d5a8174e2a78f5089d2f1fe3b40db652e7d5: Bug 1460321 - Change addons/plugins/gfx blocklist content-signature certificate r=mgoodwin
Mathieu Leplatre <mathieu@mozilla.com> - Wed, 09 May 2018 23:02:36 +0200 - rev 419778
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1460321 - Change addons/plugins/gfx blocklist content-signature certificate r=mgoodwin MozReview-Commit-ID: G90na7kHaC9
d2c504627834215bc4665d820ae01d28cfd7eb5f: Merge mozilla-central to autoland. a=merge CLOSED TREE
Brindusan Cristian <cbrindusan@mozilla.com> - Fri, 25 May 2018 03:08:34 +0300 - rev 419777
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Merge mozilla-central to autoland. a=merge CLOSED TREE
c33bba8634df638270b753a16ed85e73ad5fe27f: bug 1463901 - re-arrange some nsNSSComponent initialization/shutdown operations to avoid hanging r=jcj
David Keeler <dkeeler@mozilla.com> - Wed, 23 May 2018 15:39:38 -0700 - rev 419776
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
bug 1463901 - re-arrange some nsNSSComponent initialization/shutdown operations to avoid hanging r=jcj Before this patch, if nsNSSComponent initialization failed after allocating the XPCOM object for the component but before dispatching the load loadable roots task, BlockUntilLoadableRootsLoaded would block indefinitely in ShutdownNSS (called from ~nsNSSComponent). This patch re-arranges some things so that nsNSSComponent cleanup won't block on the load loadable roots task if it never fired. It also splits the cleanup into idempotent operations and operations that can only be run once. Unfortunately if nsNSSComponent initialization fails, Firefox is likely to exit or fail promptly anyway (since it is essential to so many other components). However, quitting outright is probably a better experience than hanging indefinitely. MozReview-Commit-ID: RWmBUV2pEU
46001e61b8bf290a1e035d75b5eaf1edb579d55d: Bug 1460787 - Change fatal assertion to warning for extremely large sized pages. r=dholbert
Yusuf Sermet <ysermet@mozilla.com> - Wed, 23 May 2018 10:06:57 -0700 - rev 419775
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1460787 - Change fatal assertion to warning for extremely large sized pages. r=dholbert MozReview-Commit-ID: 8MpvqbecU2k
4a9965aeeef32933599dd2a517f69be6d99ef51f: Bug 1186265 - Check the current interface's members. r=bz
Boris Zbarsky <bzbarsky@mit.edu> - Wed, 23 May 2018 13:56:20 -0700 - rev 419774
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1186265 - Check the current interface's members. r=bz MozReview-Commit-ID: Hfh0yyNBGE4
55bd8076423191913ac67177b1c106fdf484ce99: Bug 1186265 - Resurrect DOMQuad.bounds (deprecated) and count its uses. r=bz
Blake Kaplan <mrbkap@gmail.com> - Wed, 23 May 2018 16:56:22 -0700 - rev 419773
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1186265 - Resurrect DOMQuad.bounds (deprecated) and count its uses. r=bz I've made the returned object from .bounds not live. If that's not OK, I'll resurrect DOMBounds (removed in a previous patch). This also forces DOMQuad.toJSON() to only return the points. MozReview-Commit-ID: 10TY5oJUmTN
00fefd3eb6345155a17426015aad5b90d9e174cb: Bug 1186265 - Partially update DOMPoint, DOMQuad, DOMRect, DOMMatrix. r=bz
Blake Kaplan <mrbkap@gmail.com> - Thu, 29 Mar 2018 16:19:31 -0700 - rev 419772
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1186265 - Partially update DOMPoint, DOMQuad, DOMRect, DOMMatrix. r=bz Some notes: this does not fully bring us to compliance to the current spec. Instead, these are the fixes that I needed to make in order to make css/geometry/interfaces.html pass with the DOMPoint changes in the previous patches. I don't fully understand why that patch caused the test to fail the way it did, but it ended up being easier to fix our code than understand why the harness was falling over. The DOMQuad::QuadBounds class was the source of some confusion for me. Now that DOMRectReadOnly is a concrete class with members, I wanted to avoid wasting them. However, the spec is unclear as to whether a DOMQuad's bound's should be live -- that is because DOMQuad exposes DOMPoint, we can set its points after retrieving a QuadBounds object. Our current code is live, setting the points changes the QuadBounds. Chromium's current behavior is to never update the QuadBounds object. I've left our behavior untouched in this patch (and waste 4 doubles per QuadBounds object), but I am intending to file a bug to understand what the intent of the spec is. I wonder if the author intended the points to be DOMPointReadOnly instead. If so, we could simplify the DOMRectReadOnly code and get rid of the virtual getters, which would be nice. I also wasn't thrilled to put the DOMMatrix setters on the DOMMatrixReadOnly class, but for brevity and simplicity of implementation, I've made them public. I briefly considered making the setters protected on the ReadOnly version of the class, but I'm not convinced that having to explicitly make them public on the derived class is worth the extra copies of the names. MozReview-Commit-ID: CjdW4Nbnc6A
aae6a29b4ca3943e0ad146ab7b4373c35b779ca7: Bug 1461954: Fix nsBulletFrame's image request registration code. r=tnikkel
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 16 May 2018 15:05:54 +0200 - rev 419771
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1461954: Fix nsBulletFrame's image request registration code. r=tnikkel Ideas for a test for this welcome :). MozReview-Commit-ID: 1IpUlakeKXm
8d4723480e6c3e0a186768b0f01e23727a512225: Bug 1463026 - Avoid unnecesarily setting the toolbox buttons when reloading the page; r=jryans
Brian Birtles <birtles@gmail.com> - Thu, 24 May 2018 13:13:50 +0900 - rev 419770
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1463026 - Avoid unnecesarily setting the toolbox buttons when reloading the page; r=jryans Changeset https://hg.mozilla.org/mozilla-central/rev/00c968ee4e0c from bug 1451592 introduced a DAMP regression on several reload tests. This is because upon reloading a page we get a series of frame-update messages which tell us that we no longer have any iframes only to then tell us we do have iframes after all. As a result we update the toolbar buttons to remove the frames button only to re-add it again. This causes unnecessary updates and flicker. This patch mitigates this problem by introducing debouncing during reloading/navigating so that we only update the toolbar buttons after some timeout of inactivity if there has been a change in the frames button's state. MozReview-Commit-ID: 3CpEjLfNjbC
2d538ade0306540dd73123ea8898f3745c57fd0e: Backed out 3 changesets (bug 1464102) for browser-chrome failures on siteData/browser_siteData.js. CLOSED TREE
Narcis Beleuzu <nbeleuzu@mozilla.com> - Fri, 25 May 2018 01:42:37 +0300 - rev 419769
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Backed out 3 changesets (bug 1464102) for browser-chrome failures on siteData/browser_siteData.js. CLOSED TREE Backed out changeset 460cd874757f (bug 1464102) Backed out changeset 3c227d911b2f (bug 1464102) Backed out changeset 43b864db2e34 (bug 1464102)
c869e76b79c58780333fefa13a750bc6909ec069: Bug 1432567 - [Mac] Add a test that renders fonts from non-standard directories r=jfkthame
Haik Aftandilian <haftandilian@mozilla.com> - Tue, 22 May 2018 12:31:03 -0700 - rev 419768
Push 34048 by btara@mozilla.com at Fri, 25 May 2018 09:59:37 +0000
Bug 1432567 - [Mac] Add a test that renders fonts from non-standard directories r=jfkthame Adds a test to validate that content sandboxing is allowing content processes to access fonts from non-standard locations on the filesystem. The test copies the Fira Sans font to the root of the home directory and renders a page that should use Fira Sans when it is installed and registered with the OS. The test checks for the use of the ".LastResort" font which is an indication of the the content process failing to load the font. MozReview-Commit-ID: GPWqHdF3vhG
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip