f8b2a8bbe3e644d3f1cead1cf595fcca958360f1: Bug 929484 - Create nsDisplayTableFixedPosition to avoid display list collision when processing background image of table. r=mattwoodrow
Morris Tseng <mtseng@mozilla.com> - Fri, 05 May 2017 14:30:16 +0800 - rev 356728
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 929484 - Create nsDisplayTableFixedPosition to avoid display list collision when processing background image of table. r=mattwoodrow MozReview-Commit-ID: 2DKdqk5kbHt
0f7e0529ee3f6b98d5487c088b93b9f617ac8d53: Bug 929484 - Remove nsTableBorderBackground displayitem and nsTablePainter. r=mstange
Morris Tseng <mtseng@mozilla.com> - Fri, 05 May 2017 14:30:15 +0800 - rev 356727
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 929484 - Remove nsTableBorderBackground displayitem and nsTablePainter. r=mstange MozReview-Commit-ID: 1HmfGyBqWnf
31cfb8c2491f23a6bec8c7cee66ac25cd6de99f6: Bug 929484 - Draw each table's background on their own display item. r=mstange
Morris Tseng <mtseng@mozilla.com> - Fri, 05 May 2017 14:30:15 +0800 - rev 356726
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 929484 - Draw each table's background on their own display item. r=mstange This patch do following things: 1. Create nsDisplayTableBorderCollapse that draws all collapse border of table. 2. Don't use nsDisplayTableBorderBackground. 3. Let column and column group frame generate display items. 4. When traversing the table, also traverse the column and column group frames. 5. For each type of table frame (col group, col, row group, row and cell), draw their own background. MozReview-Commit-ID: 1s2VLv6G8xi
33df8c04309cf792b214c5c6c903a391048f5516: Bug 1357307 - Make sure gfxPrefs instance is created before accessing it. r=milan
vincentliu <vliu@mozilla.com> - Fri, 05 May 2017 14:22:51 +0800 - rev 356725
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1357307 - Make sure gfxPrefs instance is created before accessing it. r=milan
e9bb619755c4d9dbb67ada4f51d1d2b85163b8f8: Bug 1359682 - Open Netmonitor response panel when clicking on file thumbnail. r=gasolin
Michael Brennan <brennan.brisad@gmail.com> - Thu, 04 May 2017 05:07:00 +0800 - rev 356724
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1359682 - Open Netmonitor response panel when clicking on file thumbnail. r=gasolin
797a743271c6b16d27108fca38d2dfbd5a01c081: Backed out 6 changesets (bug 1360807) for ongoing hangs in test_fileReader.html and test_ipcBlob_fileReaderSync.html
Phil Ringnalda <philringnalda@gmail.com> - Thu, 04 May 2017 19:26:26 -0700 - rev 356723
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Backed out 6 changesets (bug 1360807) for ongoing hangs in test_fileReader.html and test_ipcBlob_fileReaderSync.html CLOSED TREE Backed out changeset 3a05e05fb644 (bug 1360807) Backed out changeset 9630a51eca07 (bug 1360807) Backed out changeset 41e9af8078dd (bug 1360807) Backed out changeset e59616a3997a (bug 1360807) Backed out changeset c800cb830b36 (bug 1360807) Backed out changeset 4ab091bdeda1 (bug 1360807) MozReview-Commit-ID: 1h3pcsPi2An
86bff7bb38dfc514fb51d5aed9584fa3cd2f748e: Bug 1360784 - Revert a workaround for bug 1361632. r=xidorn
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Thu, 04 May 2017 23:35:59 +0900 - rev 356722
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360784 - Revert a workaround for bug 1361632. r=xidorn MozReview-Commit-ID: FU7r2cMaQOL
bc25cff90b6ede8d18edfa2d4539c3fc2df3486a: Bug 1360471 (part 4) - Use a bitfield to represent profiler features. r=mstange.
Nicholas Nethercote <nnethercote@mozilla.com> - Mon, 01 May 2017 14:23:34 +1000 - rev 356721
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360471 (part 4) - Use a bitfield to represent profiler features. r=mstange. Currently the profiler mostly uses an array of strings to represent which features are available and in use. This patch changes the profiler core to use a uint32_t bitfield, which is a much simpler and faster representation. (nsProfiler and the profiler add-on still use the array of strings, alas.) The new ProfilerFeature type defines the values in the bitfield. One side-effect of this change is that profiler_feature_active() now can be used to query all features. Previously it was just a subset. Another side-effect is that profiler_get_available_features() no longer incorrectly indicates support for Java and stack-walking when they aren't supported. (The handling of task tracer support is unchanged, because the old code handled it correctly.)
ec6226c96adc7e2a9c4b171073892c054e393293: Bug 1360471 (part 3) - Rename various "thread name filters" identifiers as "filters". r=mstange.
Nicholas Nethercote <nnethercote@mozilla.com> - Mon, 01 May 2017 13:42:53 +1000 - rev 356720
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360471 (part 3) - Rename various "thread name filters" identifiers as "filters". r=mstange. The new names are more concise and matches common usage elsewhere (e.g. profiler_start() arguments). This patch is similar to bug 1358074 part 5.
4fc16f5a148ef525f8113593592fd41470fa7eb6: Bug 1360471 (part 2) - Rename profiler_get_features() as profiler_get_available_features(). r=mstange.
Nicholas Nethercote <nnethercote@mozilla.com> - Mon, 01 May 2017 12:07:17 +1000 - rev 356719
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360471 (part 2) - Rename profiler_get_features() as profiler_get_available_features(). r=mstange. It clarifies that it's not just the features chosen in profiler_start().
27f2289c4623727d5b8666ad1aaa23a2ee6a619a: Bug 1360471 (part 1) - Make nsIProfilerStartParams only usable in C++. r=mstange.
Nicholas Nethercote <nnethercote@mozilla.com> - Mon, 01 May 2017 11:53:18 +1000 - rev 356718
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360471 (part 1) - Make nsIProfilerStartParams only usable in C++. r=mstange. The patch also makes the |entries| and |interval| fields readonly, because they are never changed.
47c7a63f002ebf7bf9a7fd17ee71534a4d8177f6: Bug 1360291 - Produce android version codes for AArch64/ARM64 Fennec; r=nalexander
Jim Chen <nchen@mozilla.com> - Thu, 04 May 2017 19:19:31 -0400 - rev 356717
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360291 - Produce android version codes for AArch64/ARM64 Fennec; r=nalexander Add AArch64/ARM64 support to the script that produces android version codes. Use the same scheme for AArch64 as x86, since the two architectures don't overlap, and AArch64 should override ARM just like x86 should override ARM.
1b48b5adae0bbd2aae798166197ee2d44e0eb08b: Bug 1360291 - Detect NDK version number; r=nalexander
Jim Chen <nchen@mozilla.com> - Thu, 04 May 2017 19:19:31 -0400 - rev 356716
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360291 - Detect NDK version number; r=nalexander Detect the NDK major/minor version numbers, and feed that to Breakpad. For AArch64, some Breakpad headers try to workaround NDK oddities by checking the ANDROID_NDK_MAJOR_VERSION and ANDROID_NDK_MINOR_VERSION macros.
50c060199b9a5a1ee352eff6381b87c190a29c2c: Bug 1360291 - Set minimum NDK platform version to 21 for 64-bit builds; r=nalexander
Jim Chen <nchen@mozilla.com> - Thu, 04 May 2017 19:19:30 -0400 - rev 356715
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360291 - Set minimum NDK platform version to 21 for 64-bit builds; r=nalexander 64-bit is only supported in android-21 and above in the NDK.
bdfc2fa3ca8ba1a19fbf7d4613e90f185419ca05: Bug 1360629 - Update NDK on builders to include AArch64/ARM64 support; r=nalexander
Jim Chen <nchen@mozilla.com> - Thu, 04 May 2017 19:19:30 -0400 - rev 356714
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360629 - Update NDK on builders to include AArch64/ARM64 support; r=nalexander Use a new version of the packaged NDK that includes AArch64/ARM64 support and includes the 'source.properties' file, so we can detect the NDK version.
52fff3b1e209f29f139295a65f4ed40458ff1954: Bug 1352889 - Ensure that PLDHashTable's second hash doesn't have padding with 0 bits for tables with capacity larger than 2^16. r=njn
L. David Baron <dbaron@dbaron.org> - Thu, 04 May 2017 15:17:50 -0700 - rev 356713
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1352889 - Ensure that PLDHashTable's second hash doesn't have padding with 0 bits for tables with capacity larger than 2^16. r=njn PLDHashTable takes the result of the hash function and multiplies it by kGoldenRatio to ensure that it has a good distribution of bits across the 32-bit hash value, and then zeroes out the low bit so that it can be used for the collision flag. This result is called hash0. From hash0 it computes two different numbers used to find entries in the table storage: hash1 is used to find an initial position in the table to begin searching for an entry; hash2 is then used to repeatedly offset that position (mod the size of the table) to build a chain of positions to search. In a table with capacity 2^c entries, hash1 is simply the upper c bits of hash0. This patch does not change this. Prior to this patch, hash2 was the c bits below hash1, padded at the low end with zeroes when c > 16. (Note that bug 927705, changeset 1a02bec165e16f370cace3da21bb2b377a0a7242, increased the maximum capacity from 2^23 to 2^26 since 2^23 was sometimes insufficient!) This manner of computing hash2 is problematic because it increases the risk of long chains for very large tables, since there is less variation in the hash2 result due to the zero padding. So this patch changes the hash2 computation by using the low bits of hash0 instead of shifting it around, thus avoiding 0 bits in parts of the hash2 value that are significant. Note that this changes what hash2 is in all cases except when the table capacity is exactly 2^16, so it does change our hashing characteristics. For tables with capacity less than 2^16, it should be using a different second hash, but with the same amount of random-ish data. For tables with capacity greater than 2^16, it should be using more random-ish data. Note that this patch depends on the patch for bug 1353458 in order to avoid causing test failures. MozReview-Commit-ID: JvnxAMBY711
d4225b0990255df9f75157a74c249878a2f47103: Bug 1353458 - Make test_cert_blocklist more flexible about order of lines in revocations.txt. r=keeler
L. David Baron <dbaron@dbaron.org> - Thu, 04 May 2017 15:17:50 -0700 - rev 356712
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1353458 - Make test_cert_blocklist more flexible about order of lines in revocations.txt. r=keeler This allows patches to land that will change the hashtable enumeration order, which in turn changes the ordering of the lines in revocations.txt. MozReview-Commit-ID: Fyuahnpky6g
e059178907999f07218e8d26f18a919b3ac9435a: Bug 1360201 - Emit |dup| instead of |dupat 0| when BytecodeEmitter::emitDupAt is called with zero. r=shu
André Bargull <andre.bargull@gmail.com> - Thu, 27 Apr 2017 10:10:03 -0700 - rev 356711
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360201 - Emit |dup| instead of |dupat 0| when BytecodeEmitter::emitDupAt is called with zero. r=shu
ed8623eefe6ca566ebee4ae3070fba6f1e05f200: Bug 1360220 - Replace emitRequireObjectCoercible with JSOP_CHECKOBJCOERCIBLE. r=shu
André Bargull <andre.bargull@gmail.com> - Thu, 27 Apr 2017 09:24:08 -0700 - rev 356710
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1360220 - Replace emitRequireObjectCoercible with JSOP_CHECKOBJCOERCIBLE. r=shu
f9abb9c834521e7c5019bde82a1a893fa26a1d2b: Bug 1319111 - Expose URI to make security check against on LoadInfo (no LOAD_REPLACE flag). r=bz
Honza Bambas <honzab.moz@firemni.cz> - Fri, 27 Jan 2017 19:10:01 +0100 - rev 356709
Push 31768 by cbook@mozilla.com at Fri, 05 May 2017 13:17:50 +0000
Bug 1319111 - Expose URI to make security check against on LoadInfo (no LOAD_REPLACE flag). r=bz
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip