4e09e6f2c6eaa65ef4218b087171bd6706d976a1: Bug 1298218 - Tests. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Wed, 07 Sep 2016 23:19:09 -0400 - rev 469591
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
Bug 1298218 - Tests. r=mattwoodrow MozReview-Commit-ID: LW4I9M5OXc9
59d03e3235e509b5e3498d9d11f95e6253d00d0a: Bug 1298218 - Create nsDisplayFixedPosition if the element has a scrolled clip. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Wed, 24 Aug 2016 16:34:31 -0400 - rev 469590
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
Bug 1298218 - Create nsDisplayFixedPosition if the element has a scrolled clip. r=mattwoodrow MozReview-Commit-ID: Kvqs6YkeGZ
faefb3b2598889fd770e616c8daacc0017565054: Bug 1298218 - Save and restore the combined clip for the "top layer". r=tnikkel
Markus Stange <mstange@themasta.com> - Fri, 27 Jan 2017 17:33:53 +0100 - rev 469589
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
Bug 1298218 - Save and restore the combined clip for the "top layer". r=tnikkel MozReview-Commit-ID: IRfB85gVyWB
2023dadca59c6eef58385af514d349b7d3c79ab2: Bug 1298218 - Use DisplayItemClipChain for tracking clips on display items. r=mattwoodrow,tnikkel
Markus Stange <mstange@themasta.com> - Tue, 31 Jan 2017 17:07:35 -0500 - rev 469588
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
Bug 1298218 - Use DisplayItemClipChain for tracking clips on display items. r=mattwoodrow,tnikkel This is the bulk of the changes. - DisplayItemScrollClip is removed. Instead, we will have 1) ActiveScrolledRoot and 2) DisplayItemClipChain. - ActiveScrolledRoot points to a scroll frame and allows traversing up the scroll frame chain. - DisplayItemClipChain is a linked list of clips, each clip being associated with the ActiveScrolledRoot that moves this clip. - Each display item has an ActiveScrolledRoot and a clip chain. - nsDisplayItem::GetClip returns the item of the clip chain that scrolls with the item's ASR. The separation between "regular clip" and "scroll clips" mostly goes away. - Tracking clips in the display list builder's clip state happens very similarly to how regular clips used to be tracked - there's a clip chain for content descendants and a clip chain for containing block descendants. These clip chains are intersected to create the combined clip chain. - There are strict rules for the ASR of a container item: A container item's ASR should be the innermost ASR which the item has finite clipped bounds with respect to. - At some point in the future, ASRs and AGRs should be reunified, but I haven't done that yet, because I needed to limit the scope of the change. MozReview-Commit-ID: KYEpWY7qgf2
a97b00d08fbd0705812120c3b2c35ded3812a16d: Bug 1298218 - Back out bug 1284586. r=tnikkel
Markus Stange <mstange@themasta.com> - Fri, 19 Aug 2016 18:17:36 -0400 - rev 469587
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
Bug 1298218 - Back out bug 1284586. r=tnikkel MozReview-Commit-ID: FGNKyDcoEyF
d7b10f6c7982b619c8d877a9f81a7fc32f4c3fda: Bug 1298218 - Add DisplayItemClipChain. r=mattwoodrow,tnikkel
Markus Stange <mstange@themasta.com> - Fri, 27 Jan 2017 12:57:44 +0100 - rev 469586
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
Bug 1298218 - Add DisplayItemClipChain. r=mattwoodrow,tnikkel MozReview-Commit-ID: K9mg86VgK10
071bde29b52f3e2268bf2c4092835f9c03ad4e22: Bug 1298218 - Create ActiveScrolledRoot struct. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Fri, 27 Jan 2017 13:09:42 +0100 - rev 469585
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
Bug 1298218 - Create ActiveScrolledRoot struct. r=mattwoodrow MozReview-Commit-ID: Bcr801WbRmS
8eeb5e0b825b2e6a0d1ba04e04c324b0b2ec9b06: Bug 1298218 - Add the ability to know whether a background image is fixed before creating the display item. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Fri, 19 Aug 2016 19:36:57 -0400 - rev 469584
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
Bug 1298218 - Add the ability to know whether a background image is fixed before creating the display item. r=mattwoodrow With the ActiveScrolledRoot changes, we will need to set up different state on the display list builder prior to creating the nsDisplayBackgroundImage item. MozReview-Commit-ID: CgeffVPccfj
38d9a0fa515abfc32aced8d09704d40c47c6ef23: Bug 1322862 - Compare unicode strings in Python test; r=whimboo
Andreas Tolfsen <ato@mozilla.com> - Tue, 03 Jan 2017 18:45:35 +0000 - rev 469583
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
Bug 1322862 - Compare unicode strings in Python test; r=whimboo It has been known to happen that Python occassionally trips up string comparison on Windows and that this is causing intermittent issues. This patch uses unicode strings consistently so that this should not occur. MozReview-Commit-ID: BAdHfiLZzuQ
0d31bc70ba466848e3b44d42c9298bf4a4297a6d: Bug 1322862 - Make __webDriverArguments et al. content safe; r=automatedtester
Andreas Tolfsen <ato@mozilla.com> - Sat, 10 Dec 2016 16:15:53 -1000 - rev 469582
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
Bug 1322862 - Make __webDriverArguments et al. content safe; r=automatedtester Properties created in a more privileged scope than content cause permission denied errors when they are accessed from a less privileged scope. This is the case when we assign a document unload handler from chrome to a sandbox with content privileges. A permission denied error will be thrown if this handler is inspected from the code evaluated inside the sandbox. By cloning the properties along with their functions and wrapping their reflectors, we can ensure they can be safely inspected from content. MozReview-Commit-ID: Hy5MYvdTsv8
abf765aee76c4289cdbe9014e6efb70fb893f205: bug 1303383 - enable 5 Amazon root CAs for EV r=jcj
David Keeler <dkeeler@mozilla.com> - Tue, 31 Jan 2017 16:05:35 -0800 - rev 469581
Push 43782 by mdeboer@mozilla.com at Thu, 02 Feb 2017 14:01:18 +0000
bug 1303383 - enable 5 Amazon root CAs for EV r=jcj MozReview-Commit-ID: JRs7CWwafSK
93d4215d52e9875e6036f1e4eb7d12d5a3670d8b: Bug 1310703 - Add support for the pingsender to the Telemetry code; r?Dexter draft
Gabriele Svelto <gsvelto@mozilla.com> - Tue, 17 Jan 2017 14:53:00 +0100 - rev 469580
Push 43781 by gsvelto@mozilla.com at Thu, 02 Feb 2017 13:59:37 +0000
Bug 1310703 - Add support for the pingsender to the Telemetry code; r?Dexter MozReview-Commit-ID: 6XcljmJCbFk
2d3e0f26f06e71b1cca8c8dc8b63727686e2c937: Bug 1310703 - Use the ID generated by the crashreporter client when sending a crash ping so that server-side deduplication works correctly; r?Dexter draft
Gabriele Svelto <gsvelto@mozilla.com> - Mon, 16 Jan 2017 18:17:02 +0100 - rev 469579
Push 43781 by gsvelto@mozilla.com at Thu, 02 Feb 2017 13:59:37 +0000
Bug 1310703 - Use the ID generated by the crashreporter client when sending a crash ping so that server-side deduplication works correctly; r?Dexter MozReview-Commit-ID: JvqY0Lu75HQ
00c4988e95f79116e04d996c2991abfada33490a: Bug 1310703 - Make the crashreporter client send a crash ping via the ping sender executable; r?ted draft
Gabriele Svelto <gsvelto@mozilla.com> - Mon, 16 Jan 2017 18:14:17 +0100 - rev 469578
Push 43781 by gsvelto@mozilla.com at Thu, 02 Feb 2017 13:59:37 +0000
Bug 1310703 - Make the crashreporter client send a crash ping via the ping sender executable; r?ted MozReview-Commit-ID: LKKpO94smLk
677fa589d3d026e0baf7398b049e3360b09a2486: Bug 1310703 - Introduce the pingsender executable; r?ted draft
Gabriele Svelto <gsvelto@mozilla.com> - Mon, 16 Jan 2017 17:39:22 +0100 - rev 469577
Push 43781 by gsvelto@mozilla.com at Thu, 02 Feb 2017 13:59:37 +0000
Bug 1310703 - Introduce the pingsender executable; r?ted MozReview-Commit-ID: HxU41s0yamZ
14e91c31f2a055bc4440a8edb92c1761d3566048: Bug 1336028 NativeKey::GetFollowingCharMessage() should take newer char message when found char message and removed message from the queue is different but their scancode indicates same physical key r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 02 Feb 2017 22:46:43 +0900 - rev 469576
Push 43780 by masayuki@d-toybox.com at Thu, 02 Feb 2017 13:51:09 +0000
Bug 1336028 NativeKey::GetFollowingCharMessage() should take newer char message when found char message and removed message from the queue is different but their scancode indicates same physical key r?m_kato NativeKey::GetFollowingCharMessage() may remove a char message which is different from previously found message in the queue because hacky keyboard layout or utility can overwrite the wParam when it's removed from the queue. Now, we should assume that newer message, i.e., actually removed from the queue, is the expected message by the user. See bug 1336028 comment 0 for the actual scenarios which are collected by crash reports. https://bugzilla.mozilla.org/show_bug.cgi?id=1336028#c0 MozReview-Commit-ID: 9ZgukHH1vfi
2434eb787bb3837f0efa84a4e4a74fb006cbe45e: Bug 1335670 NativeKey should dispatch consumed keydown event when it receives WM_NULL at removing WM_*CHAR from the queue and the original message has gone r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 02 Feb 2017 22:43:20 +0900 - rev 469575
Push 43780 by masayuki@d-toybox.com at Thu, 02 Feb 2017 13:51:09 +0000
Bug 1335670 NativeKey should dispatch consumed keydown event when it receives WM_NULL at removing WM_*CHAR from the queue and the original message has gone r?m_kato Currently, NativeKey::GetFollowingCharMessage() tries 5 times to remove found char message from the queue. It was enough when we found this issue at developing Metrofox. However, this hack is not enough for some odd keyboard layouts because we see some crash reports which gives up to remove a char message from the queue because 5 WM_NULL messages are returned. For preventing this crash, we should check if there is the message which is trying to remove from the queue when NativeKey receives WM_NULL. Then, when there is no key message in the queue or next key message becomes non-char message,, NativeKey should dispatch consumed keydown event because we can assume that the key operation may have already been handled or canceled. Otherwise, NativeKey should retry to remove the message again (until 50 times!, it's just enough big magic number, there is no concrete reason). MozReview-Commit-ID: 1c6Y4OoQdrP
6467514ca02b2a79d764b6fca04b1f01d0cd6ccb: Bug 1336084 - fix indentation after bug 1120441 r?ahunt draft
Julien Cristau <jcristau@mozilla.com> - Thu, 02 Feb 2017 14:24:54 +0100 - rev 469574
Push 43779 by jcristau@mozilla.com at Thu, 02 Feb 2017 13:44:48 +0000
Bug 1336084 - fix indentation after bug 1120441 r?ahunt MozReview-Commit-ID: IsN11wdccin
8c1ba992763414e32bd8f1c6d56aacce3ddd2bb2: Bug 1336070 - Enable eslint no-undef for browser/, apart from components/ and base/content/. r?Mossop draft
Mark Banner <standard8@mozilla.com> - Thu, 02 Feb 2017 09:08:42 +0000 - rev 469573
Push 43778 by bmo:standard8@mozilla.com at Thu, 02 Feb 2017 13:34:46 +0000
Bug 1336070 - Enable eslint no-undef for browser/, apart from components/ and base/content/. r?Mossop MozReview-Commit-ID: CJtpm8zlLxa
77964a98ecd94305628322a479ff5012e2e57e2d: Bug 1335971: Allow uploading on the client side on Intel hardware. r=mattwoodrow draft
Bas Schouten <bschouten@mozilla.com> - Thu, 02 Feb 2017 13:24:57 +0000 - rev 469572
Push 43777 by bschouten@mozilla.com at Thu, 02 Feb 2017 13:28:28 +0000
Bug 1335971: Allow uploading on the client side on Intel hardware. r=mattwoodrow MozReview-Commit-ID: GeVYccWK7xY
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip