b3a76122631fa682a9f659c6ea2228985983c123: Bug 1431573 - Part 9: Implement toggle pause/resume function by key board. r?gl draft
Daisuke Akatsuka <dakatsuka@mozilla.com> - Mon, 12 Mar 2018 13:08:23 +0900 - rev 766120
Push 102230 by bmo:dakatsuka@mozilla.com at Mon, 12 Mar 2018 09:02:24 +0000
Bug 1431573 - Part 9: Implement toggle pause/resume function by key board. r?gl MozReview-Commit-ID: 7p1Iu54gIR8
e6a8508fd23fe1668a86a3a08d87f6b4a6241ddc: Bug 1431573 - Part 8: Implement progress bar in keyframes. r?gl draft
Daisuke Akatsuka <dakatsuka@mozilla.com> - Mon, 12 Mar 2018 13:08:01 +0900 - rev 766119
Push 102230 by bmo:dakatsuka@mozilla.com at Mon, 12 Mar 2018 09:02:24 +0000
Bug 1431573 - Part 8: Implement progress bar in keyframes. r?gl MozReview-Commit-ID: GE5Of8VklAJ
172a1d9adca77696ce2f50173c500b6482893e56: Bug 1431573 - Part 7: Implement scrubber. r?gl draft
Daisuke Akatsuka <dakatsuka@mozilla.com> - Mon, 12 Mar 2018 12:56:09 +0900 - rev 766118
Push 102230 by bmo:dakatsuka@mozilla.com at Mon, 12 Mar 2018 09:02:24 +0000
Bug 1431573 - Part 7: Implement scrubber. r?gl MozReview-Commit-ID: B6CeCDWawym
9e22bd966d2ff4b39d7da1a1f36694cb29f66e75: Bug 1435373 - Map changes from shape highlighter to correct CSS rules. r=pbro draft
Razvan Caliman <rcaliman@mozilla.com> - Mon, 19 Feb 2018 17:45:06 +0100 - rev 766117
Push 102229 by bmo:rcaliman@mozilla.com at Mon, 12 Mar 2018 08:43:27 +0000
Bug 1435373 - Map changes from shape highlighter to correct CSS rules. r=pbro - Emit shape change events from highlighter - Wrap shape highlighter with in-context shape editor singleton - Link text properties from Rule view into in-context shapes editor - Write changes to corresponding rule instead of inline style - Hide shape highlighter on node change or TextProperty disabled/overwritten - Remove functionality to restore shape editor on refresh - Refactor and consolidate shape point hover behaviour (still to do: internalize remaining logic for point hover from rules.js and highlighter-overlay.js) - Update unit tests MozReview-Commit-ID: JiMTqODgcjU
e0fad10f4f7c81c8e6b5251ecef689c185b0a045: Bug 1435373 - Minor refactor for shape output string guarding against empty this.geometryBox. Round values in getDistance() util function to avoid verbose precision. draft
Razvan Caliman <rcaliman@mozilla.com> - Mon, 19 Feb 2018 17:51:10 +0100 - rev 766116
Push 102229 by bmo:rcaliman@mozilla.com at Mon, 12 Mar 2018 08:43:27 +0000
Bug 1435373 - Minor refactor for shape output string guarding against empty this.geometryBox. Round values in getDistance() util function to avoid verbose precision. MozReview-Commit-ID: IBB4mkvAu6h
f99f01e3194462084f4390a2065a744f55710bb2: Bug 1440195 Do not Jitter if NSS is not initialized r?keeler draft
Tom Ritter <tom@mozilla.com> - Fri, 09 Mar 2018 21:27:44 -0600 - rev 766115
Push 102228 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:24:10 +0000
Bug 1440195 Do not Jitter if NSS is not initialized r?keeler MozReview-Commit-ID: Dgfi8Z1hHfB
225608286c899db69a68f1810ede43ef4fbc1de2: Bug 1440195 Actually integrate the context mix-in into the hash function calculation r?baku draft
Tom Ritter <tom@mozilla.com> - Fri, 09 Mar 2018 16:26:56 -0600 - rev 766114
Push 102228 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:24:10 +0000
Bug 1440195 Actually integrate the context mix-in into the hash function calculation r?baku MozReview-Commit-ID: 4k7w683UJOY
06c0423ae42837f2aaf55f957f40d05e66bcc363: Bug 1440195 Address CSS Animations r?birtles draft
Tom Ritter <tom@mozilla.com> - Mon, 05 Mar 2018 15:58:46 -0600 - rev 766113
Push 102228 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:24:10 +0000
Bug 1440195 Address CSS Animations r?birtles For now, we are going to make _all_ CSS Animations related timer fuzzing only applicable in Resist Fingerprinting Mode (addressing the last couple that had not already been configured that way.) We hardcode their content mix-ins as zero, but leave comments indicating how they should behave. MozReview-Commit-ID: KhmV7wO8Pt5
491f8d756f9dc31b998040294d561a337334d7cb: Bug 1440195 Add a random context seed to the Performance APIs r?baku draft
Tom Ritter <tom@mozilla.com> - Mon, 05 Mar 2018 16:29:40 -0600 - rev 766112
Push 102228 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:24:10 +0000
Bug 1440195 Add a random context seed to the Performance APIs r?baku We attach it to WorkerPrivate and DOMNavigationTiming so it will be re-used when it should. WorkerPrivate is used in the Performance APIs, Performance Storage Worker, and Event. DOMNavigationTiming is used only in the Performance APIs, but the crucial part is that when the individual DOMNavigationTiming object is re-used, so will the context seed. This in particular came up with the nav2_test_document_open.html Web Platform Test which illustrated the fact that even if you .open() a new document, the performance navigation data is not supposed to change. MozReview-Commit-ID: GIv6biEo2jY
aa061424ec6f9e689d20ad4808a30f519ad6b5de: Bug 1440195 Add a random context seed for AudioContext and MediaStream r?baku draft
Tom Ritter <tom@mozilla.com> - Thu, 01 Mar 2018 11:00:12 -0600 - rev 766111
Push 102228 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:24:10 +0000
Bug 1440195 Add a random context seed for AudioContext and MediaStream r?baku MozReview-Commit-ID: sHpVCgd8Fs
f4c9b198a20bc0060fa9a5ddd55222bb61eebea4: Bug 1440195 For timestamps that are absolute, specify a null context pointer r?baku draft
Tom Ritter <tom@mozilla.com> - Wed, 28 Feb 2018 15:37:26 -0600 - rev 766110
Push 102228 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:24:10 +0000
Bug 1440195 For timestamps that are absolute, specify a null context pointer r?baku Note that by not using the same context pointer for all timestamps within a single 'communication group' (that is, all things that can communication to each other in JavaScript), it's possible to observe time going backwards. Imagine comparing performance.timeOrigin + performance.now() < new File([], "").lastModified In theory this should always be true. However, if performance.now() was jittered up (using one context pointer, because it is a relative timestamp) and File was jittered down (using a null context pointer, because it is an absolute timestamp) then this may evaluate to False. I think this is okay. MozReview-Commit-ID: BfgbmGS8XdD
a55c09002b3a60de28c3ca32c80a9dc864bc889b: Bug 1440195 Add a per-context mix-in value for our Timer Precision Reduction Functions r?baku draft
Tom Ritter <tom@mozilla.com> - Fri, 09 Mar 2018 16:22:37 -0600 - rev 766109
Push 102228 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:24:10 +0000
Bug 1440195 Add a per-context mix-in value for our Timer Precision Reduction Functions r?baku We need to include a seed for each context (origin, iframe, worker, etc) we reduce the time precision of. This prevents a replay attack of the random midpoint sequence. MozReview-Commit-ID: EFoHev1SrTM
e1c28d924fd839418757afdc7254fa59dc0ca147: Bug 1443943 Allow internal callers of performance.now() to opt-out of clamping/jittering r?baku draft
Tom Ritter <tom@mozilla.com> - Fri, 09 Mar 2018 20:12:53 -0600 - rev 766108
Push 102227 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:22:42 +0000
Bug 1443943 Allow internal callers of performance.now() to opt-out of clamping/jittering r?baku PresShell only uses performane.now to track refresh times, and notify internal observers. We can provide more accurate times by not clamping and jittering these numbers. MozReview-Commit-ID: FkDGJhrLeAy
c189bf3259c47503700d0674b8abca593d0eb165: Bug 1443943 Do not clamp/jitter event timestamps if it's a system principal r?baku draft
Tom Ritter <tom@mozilla.com> - Fri, 09 Mar 2018 10:00:23 -0600 - rev 766107
Push 102227 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:22:42 +0000
Bug 1443943 Do not clamp/jitter event timestamps if it's a system principal r?baku This patch has an annoying gap in it. I follow the pointer chain up like so: mPresContext->Document()->NodePrincipal() However, sometimes either mPresContext or mPresContext->Document() is null. I don't know why. MozReview-Commit-ID: KvVJpvu4elN
0cfc411f6ec38c72872da94d08c3c797cc1d98a6: Bug 1443943 Do not clamp/jitter in the JS Engine if it's system context r?luke draft
Tom Ritter <tom@mozilla.com> - Fri, 09 Mar 2018 09:49:28 -0600 - rev 766106
Push 102227 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:22:42 +0000
Bug 1443943 Do not clamp/jitter in the JS Engine if it's system context r?luke MozReview-Commit-ID: LqL7xaYoHCT
2b684038d605c7266cba0d607d9aacf2c9bfa16b: Bug 1443943 Port the performance APIs only to only clamping/jittering on non-System Principal r?baku draft
Tom Ritter <tom@mozilla.com> - Fri, 09 Mar 2018 09:29:33 -0600 - rev 766105
Push 102227 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 07:22:42 +0000
Bug 1443943 Port the performance APIs only to only clamping/jittering on non-System Principal r?baku MozReview-Commit-ID: FKYLI5Yc1kX
a8358d31a3eda062a872543aa3e55122b2dae18c: Bug 1428976 - Part 3: fix visibility of devtool panels draft
Pierre de La Morinerie <kemenaran@gmail.com> - Fri, 09 Mar 2018 13:19:41 +0530 - rev 766104
Push 102226 by bmo:kemenaran@gmail.com at Mon, 12 Mar 2018 05:43:53 +0000
Bug 1428976 - Part 3: fix visibility of devtool panels MozReview-Commit-ID: CquQMNkX3qo
2b75b8f1eca38cee42c885997cfa8ae606f7d99f: Bug 1428976 - Part 2: refactor panel visibility tests draft
Pierre de La Morinerie <kemenaran@gmail.com> - Fri, 09 Mar 2018 13:19:06 +0530 - rev 766103
Push 102226 by bmo:kemenaran@gmail.com at Mon, 12 Mar 2018 05:43:53 +0000
Bug 1428976 - Part 2: refactor panel visibility tests MozReview-Commit-ID: 5prJZumM9cJ
792ab6ce1a7b7500403608acc4e4312cb360b6f7: Bug 1428976 - Part 1: fix typo in panels visibility test draft
Pierre de La Morinerie <kemenaran@gmail.com> - Thu, 08 Mar 2018 17:01:01 +0530 - rev 766102
Push 102226 by bmo:kemenaran@gmail.com at Mon, 12 Mar 2018 05:43:53 +0000
Bug 1428976 - Part 1: fix typo in panels visibility test MozReview-Commit-ID: 3cDmVJ0h9Ba
fd5f9583395905c77ad9724cfb4d82435a082317: Bug 1440195 Do not Jitter if NSS is not initialized r?keeler draft
Tom Ritter <tom@mozilla.com> - Fri, 09 Mar 2018 21:27:44 -0600 - rev 766101
Push 102225 by bmo:tom@mozilla.com at Mon, 12 Mar 2018 05:33:22 +0000
Bug 1440195 Do not Jitter if NSS is not initialized r?keeler MozReview-Commit-ID: Dgfi8Z1hHfB
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip