a1af1c31b07afcb01e8d70a91e869c15c854ffca: Bug 1273661 part 1. Add a way to construct a callback object without calling HoldJSObjects. r=smaug
Boris Zbarsky <bzbarsky@mit.edu> - Wed, 18 May 2016 12:23:35 -0400 - rev 298276
Push 77097 by bzbarsky@mozilla.com at Sat, 21 May 2016 03:13:50 +0000
Bug 1273661 part 1. Add a way to construct a callback object without calling HoldJSObjects. r=smaug
fdef8e56876622d669553bdf67524a39df1aab9b: Bug 1272651. Fix fallback loading of <embed> inside an <object> with no type attribute to actually work reliably. r=qdot
Boris Zbarsky <bzbarsky@mit.edu> - Fri, 20 May 2016 23:13:17 -0400 - rev 298275
Push 77097 by bzbarsky@mozilla.com at Sat, 21 May 2016 03:13:50 +0000
Bug 1272651. Fix fallback loading of <embed> inside an <object> with no type attribute to actually work reliably. r=qdot
93d5271f033292f898407d8cb1a1a80721a0ab5d: Bug 909633. Remove the HTML Microdata API, since no one else ended up implementing it and now it's been removed from the spec. r=bkelly,jgraham
Boris Zbarsky <bzbarsky@mit.edu> - Fri, 20 May 2016 23:13:17 -0400 - rev 298274
Push 77097 by bzbarsky@mozilla.com at Sat, 21 May 2016 03:13:50 +0000
Bug 909633. Remove the HTML Microdata API, since no one else ended up implementing it and now it's been removed from the spec. r=bkelly,jgraham
f66a5b9da35f355aa112cde5018d727246ffcb32: Bug 1271714 - Test.
Markus Stange <mstange@themasta.com> - Thu, 19 May 2016 15:06:04 -0400 - rev 298273
Push 77096 by tnikkel@gmail.com at Sat, 21 May 2016 03:01:09 +0000
Bug 1271714 - Test. MozReview-Commit-ID: 7dKuI80NEjr
557c5dbd25a169664766123f8c3f6a75a8e392f3: Bug 1271714. When creating the wrap list item that contains the display list for a frame make sure to use a scroll clip that includes content in the display list. r=mstange
Timothy Nikkel <tnikkel@gmail.com> - Fri, 20 May 2016 22:00:57 -0500 - rev 298272
Push 77096 by tnikkel@gmail.com at Sat, 21 May 2016 03:01:09 +0000
Bug 1271714. When creating the wrap list item that contains the display list for a frame make sure to use a scroll clip that includes content in the display list. r=mstange In nsIFrame::BuildDisplayListForChild for certain types of frames we create wrap list items to wrap the constructed display list to make those items inseperable. We were using the current scroll clip by default when creating these items, but that scroll clip may not contain all the content in the display list if we traversed into an out of flow frame whose containing block is an ancestor of the current frame. The CurrentAncestorScrollClipForStackingContextContents keeps track of exactly this. (Its name might be a little misleading as we may not be dealing with a true stacking context here. Nevertheless it does contain the correct clip.)
03f0242deea7a19d40f16fda32830a80584fbae1: Bug 1274037 - Rename the gecko.mstone and gecko.buildID prefs to dom.apps.lastUpdate.* r=fabrice
L. David Baron <dbaron@dbaron.org> - Fri, 20 May 2016 19:57:32 -0700 - rev 298271
Push 77095 by dbaron@mozilla.com at Sat, 21 May 2016 02:57:53 +0000
Bug 1274037 - Rename the gecko.mstone and gecko.buildID prefs to dom.apps.lastUpdate.* r=fabrice MozReview-Commit-ID: AkFkFhyUNrX
f81a68cdd9f192c2f85ac0aca1a6d7be892a0335: Bug 1274041 - Make child process write its memory map to a different file name. r=jesup
L. David Baron <dbaron@dbaron.org> - Fri, 20 May 2016 19:57:31 -0700 - rev 298270
Push 77095 by dbaron@mozilla.com at Sat, 21 May 2016 02:57:53 +0000
Bug 1274041 - Make child process write its memory map to a different file name. r=jesup This makes the child process write its memory map to a different file name, just like it does for the jprof log. It tries to share the variables between the two so that they're both connected in the code and consistent with each other. Note that I haven't yet written the patch to make jprof.cpp *read* the map from that file, so this currently requires manually renaming the generated map with the numeric suffix to jprof-map in order to run jprof. I should probably write that patch eventually, but I haven't actually needed to. This at least prevents the child process's map file from being overwritten by the parent's a fraction of a second later. MozReview-Commit-ID: 7L4wT9BdQYI
a634e9b19a3b2fb41f9bbd15683d0f7a7e6a85ed: Bug 1274041 - Initialize jprof in child process. r=jesup
L. David Baron <dbaron@dbaron.org> - Fri, 20 May 2016 19:57:31 -0700 - rev 298269
Push 77095 by dbaron@mozilla.com at Sat, 21 May 2016 02:57:53 +0000
Bug 1274041 - Initialize jprof in child process. r=jesup This makes a function call in XRE_InitChildProcess for the child process that currently exists in XREMain::XRE_mainStartup for the parent process. This allows signals that jprof uses to be sent to a child process to profile that child process. MozReview-Commit-ID: CeWnYl4LJyA
b4dd21453f98fbaa70f7f851393b40f1cb019d57: Bug 1274041 - Actually define JPROF_STATIC as it was meant to be defined. r=jesup
L. David Baron <dbaron@dbaron.org> - Fri, 20 May 2016 19:57:31 -0700 - rev 298268
Push 77095 by dbaron@mozilla.com at Sat, 21 May 2016 02:57:53 +0000
Bug 1274041 - Actually define JPROF_STATIC as it was meant to be defined. r=jesup I've had this in my tree for a while; it just fixes what look like a silly mistake. MozReview-Commit-ID: I7mSKXTSWqo
3ef68cc366bd813a64fe812b159217920d01e07c: Bug 1274486 - Disable D3D11 for more igd* DLLs - r=cpearce
Gerald Squelart <gsquelart@mozilla.com> - Fri, 20 May 2016 15:31:12 +1000 - rev 298267
Push 77094 by gsquelart@mozilla.com at Sat, 21 May 2016 02:40:16 +0000
Bug 1274486 - Disable D3D11 for more igd* DLLs - r=cpearce MozReview-Commit-ID: JXx1AvoJ5Cx
c8aa1182309ba12b21ee12641b57a53f4a419f5c: Bug 1271163 - Disable D3D11 for atidxx64.dll 8.17.10.644 - r=cpearce
Gerald Squelart <gsquelart@mozilla.com> - Fri, 20 May 2016 12:25:29 +1000 - rev 298266
Push 77093 by gsquelart@mozilla.com at Sat, 21 May 2016 02:39:07 +0000
Bug 1271163 - Disable D3D11 for atidxx64.dll 8.17.10.644 - r=cpearce MozReview-Commit-ID: Cl35HRtHFEm
b0c9aee8f2950a929b25c5a9da5aefb1d595aa9f: Bug 1271829 - Propagate MSVC -arch switch to nss. r=glandium
Ralph Giles <giles@mozilla.com> - Fri, 13 May 2016 14:16:49 -0700 - rev 298265
Push 77092 by rgiles@mozilla.com at Sat, 21 May 2016 02:36:23 +0000
Bug 1271829 - Propagate MSVC -arch switch to nss. r=glandium This updates the nss build to require SSE2 instructions on win32. By default nss builds with -arch:IA32 for maximum compatibility. Firefox 49 dropped support for non-SSE2 platforms, so propagate that to the nss external build. XCFLAGS come after the nss build's default settings, and the last -arch switch will override the previous ones. Bump CLOBBER because we've had trouble with file removal permission errors on integration builds. MozReview-Commit-ID: 2lfDq0e0T7Y
040014a28b11a0c3aec7f7dfa69e0c1f4125141d: Bug 1271829 - Don't clobber XCFLAGS building nss. r=glandium
Ralph Giles <giles@mozilla.com> - Fri, 13 May 2016 14:13:39 -0700 - rev 298264
Push 77092 by rgiles@mozilla.com at Sat, 21 May 2016 02:36:23 +0000
Bug 1271829 - Don't clobber XCFLAGS building nss. r=glandium Previously, this clobbered the XCFLAGS set by MOZ_FOLD_LIBS_FLAGS. Combine them instead so we can pass multiple options through this override mechanism. This is a behaviour change building with --enable-llvm-hacks. MozReview-Commit-ID: 4WP0asnc7Z6
e1525aa98cd1c08a2c343c577a8d68ff95fa4641: bug 1264771 - randomize key IDs in WebCrypto r=ttaubert
David Keeler <dkeeler@mozilla.com> - Wed, 04 May 2016 12:48:37 -0700 - rev 298263
Push 77091 by dkeeler@mozilla.com at Sat, 21 May 2016 02:32:31 +0000
bug 1264771 - randomize key IDs in WebCrypto r=ttaubert To import private keys, WebCrypto creates a generic PKCS#11 object with a chosen key ID with PK11_CreateGenericObject and then looks up that object as a SECKEYPrivateKey using PK11_FindKeyByKeyID. It turns out that this is only safe to do as long as the ID is unique. If another SECKEYPrivateKey exists that has the same key ID (realistically this will only happen if an identical key is imported again), PK11_FindKeyByKeyID may return the other key. Since SECKEYPrivateKey objects are unique and not meant to be shared, this causes problems in that when one key is destroyed, the resources backing the other key are no longer valid, and any cryptographic operations using that key will fail. The solution is to use random IDs and check for preexisting keys. NSS doesn't yet expose an elegant API for this, but this patch implements a workaround. MozReview-Commit-ID: EvYMZxnBxTv
b99740af9c1a838201e83823c398cf4b298058df: Bug 1272165 - Localize the use of #ifdefs to select the fling animation. r=kats
Botond Ballo <botond@mozilla.com> - Mon, 16 May 2016 18:53:23 -0400 - rev 298262
Push 77090 by bballo@mozilla.com at Sat, 21 May 2016 02:31:56 +0000
Bug 1272165 - Localize the use of #ifdefs to select the fling animation. r=kats This patch also renames FlingOverScrollerAnimation to AndroidFlingAnimation, and moves it to the newly added files AndroidAPZ.{h,cpp}. MozReview-Commit-ID: LXADdGL4SKh
db4b2156f1851b43f1d71ec60577b8992365dc29: Bug 1272165 - Move the logic for determining whether to accelerate a fling into FlingAnimation. r=kats
Botond Ballo <botond@mozilla.com> - Mon, 16 May 2016 18:23:55 -0400 - rev 298261
Push 77090 by bballo@mozilla.com at Sat, 21 May 2016 02:31:56 +0000
Bug 1272165 - Move the logic for determining whether to accelerate a fling into FlingAnimation. r=kats MozReview-Commit-ID: 41GGRtdlcAU
43fb74c6ceb4bd1145e436b3f0581bd007559f97: Bug 1272165 - Move FlingAnimation into its own file and rename it to GenericFlingAnimation. r=kats
Botond Ballo <botond@mozilla.com> - Mon, 16 May 2016 18:08:24 -0400 - rev 298260
Push 77090 by bballo@mozilla.com at Sat, 21 May 2016 02:31:56 +0000
Bug 1272165 - Move FlingAnimation into its own file and rename it to GenericFlingAnimation. r=kats MozReview-Commit-ID: EAksmwgJdax
4bd37f45a03ef34878741daec8a1454109561547: Bug 1272165 - Localize the use of #ifdefs to select the overscroll effect. r=kats
Botond Ballo <botond@mozilla.com> - Wed, 11 May 2016 20:58:19 -0400 - rev 298259
Push 77090 by bballo@mozilla.com at Sat, 21 May 2016 02:31:56 +0000
Bug 1272165 - Localize the use of #ifdefs to select the overscroll effect. r=kats MozReview-Commit-ID: IaIUhrlrhZS
84d20f2a388e85c1c4bb411561ecc13323fc9d7c: Bug 1272165 - Move OverscrollAnimation into a separate file Overscroll.h. r=kats
Botond Ballo <botond@mozilla.com> - Wed, 11 May 2016 20:40:46 -0400 - rev 298258
Push 77090 by bballo@mozilla.com at Sat, 21 May 2016 02:31:56 +0000
Bug 1272165 - Move OverscrollAnimation into a separate file Overscroll.h. r=kats MozReview-Commit-ID: DaDJEZJ7EBJ
efb43f34c4f59851f4b5416769c423b504b11b24: Bug 1272025 - Add preference to use volatile storage with Places database; r=mak
Gregory Szorc <gps@mozilla.com> - Wed, 11 May 2016 11:00:37 -0700 - rev 298257
Push 77089 by gszorc@mozilla.com at Sat, 21 May 2016 02:29:27 +0000
Bug 1272025 - Add preference to use volatile storage with Places database; r=mak We have data showing that the Places SQLite database can consume gigabytes of I/O during Firefox test automation jobs. This is because a number of tests load pages as rapdily as possible, effectively stress testing Places and SQLite. As the SQLite database is committed to, we incur I/O for the WAL journal and when flushing/synchronizing commits. This can add up to a lot of overhead, especially on spinning disks. It is important for Places to run during many tests. But it isn't necessarily important to run with robust I/O guarantees: SQLite itself has tests that ensure different journal and synchronizing modes work as advertised. This commit introduces a preference that changes the SQLite journal and synchronization modes to be less robust. We use an in-memory journal so no I/O is incurred for journal writing. We disable synchronization during commit so no expensive file(system) flushing is performed. Because setting this preference would be dangerous for end users, we only honor the pref if a scary sounding environment variable is set. Hopefully that's enough of an obstacle to prevent people from footgunning themselves. A preliminary Try run reveals this has the potential to shave hundreds of megabytes of I/O from various jobs. Although this commit stops short of changing the configuration in automation to use the new volatile storage preference. MozReview-Commit-ID: KCoDVzwkSbg
(0) -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip