8476823da14377196e46f8dbf77b7cb1bba61275: Bug 1386922 - Add learn more link to autofill address, r=MattN,lchang draft
Scott Wu <scottcwwu@gmail.com> - Fri, 08 Sep 2017 16:37:47 +0800 - rev 662799
Push 79194 by bmo:scwwu@mozilla.com at Tue, 12 Sep 2017 04:27:40 +0000
Bug 1386922 - Add learn more link to autofill address, r=MattN,lchang MozReview-Commit-ID: LloJRy8srb1
eff6ba1e803ad4663e0b0755162959c16c2dfa47: Bug 1398999 - nsDequeFunctor::operator() doesn't need to return anything - r?froydnj draft
Gerald Squelart <gsquelart@mozilla.com> - Thu, 09 Feb 2017 14:06:36 +1100 - rev 662798
Push 79193 by gsquelart@mozilla.com at Tue, 12 Sep 2017 04:14:56 +0000
Bug 1398999 - nsDequeFunctor::operator() doesn't need to return anything - r?froydnj Its return value is never used, and most implementations return nullptr anyway. MozReview-Commit-ID: 8rxC053mmE8
575d870c0f2acdde5d60c08556abc8b261cef979: Bug 1398965 - Fold memory/mozjemalloc into memory/build. r?njn draft
Mike Hommey <mh+mozilla@glandium.org> - Thu, 31 Aug 2017 16:43:19 +0900 - rev 662797
Push 79192 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:14:54 +0000
Bug 1398965 - Fold memory/mozjemalloc into memory/build. r?njn The files relevant to the memory allocator are currently spread between memory/mozjemalloc and memory/build, and the distinction was historically from sharing some Mozilla-specific things between mozjemalloc and jemalloc3. That distinction is not useful anymore, so we fold everything together. As we will likely rename the allocator at some point in the future, it is preferable to move away from the mozjemalloc directory rather than in its direction.
065721f5703fd5b1dfe593e988ec448661459ebf: Bug 1398965 - Fold memory/mozjemalloc into memory/build. r?njn draft
Mike Hommey <mh+mozilla@glandium.org> - Thu, 31 Aug 2017 16:43:19 +0900 - rev 662796
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1398965 - Fold memory/mozjemalloc into memory/build. r?njn The files relevant to the memory allocator are currently spread between memory/mozjemalloc and memory/build, and the distinction was historically from sharing some Mozilla-specific things between mozjemalloc and jemalloc3. That distinction is not useful anymore, so we fold everything together. As we will likely rename the allocator at some point in the future, it is preferable to move away from the mozjemalloc directory rather than in its direction.
91b6954443bff535383f8d3abbb07927d0ff214f: Bug 1398965 - Remove MOZ_JEMALLOC_IMPL in favor of MOZ_MEMORY_IMPL. r?njn draft
Mike Hommey <mh+mozilla@glandium.org> - Thu, 31 Aug 2017 16:28:07 +0900 - rev 662795
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1398965 - Remove MOZ_JEMALLOC_IMPL in favor of MOZ_MEMORY_IMPL. r?njn In practice, they mean the same thing, and there's only one place where MOZ_JEMALLOC_IMPL was used.
114d87a3943b48a8cc1e9ca498bd7e7a306c95ac: Bug 1385239 - Part 3. A test case of putting a translated filtered element inside an SVG mask. r=mstange
cku <cku@mozilla.com> - Wed, 23 Aug 2017 14:45:42 +0800 - rev 662794
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1385239 - Part 3. A test case of putting a translated filtered element inside an SVG mask. r=mstange MozReview-Commit-ID: AqSL8Gb5R46
9a6413d1fd0a02e60c109aa9f324288911f8ee52: Bug 1385239 - Part 2. Remove aTransform parameter from PaintFilteredFrame. r=mstange
cku <cku@mozilla.com> - Fri, 25 Aug 2017 17:51:58 +0800 - rev 662793
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1385239 - Part 2. Remove aTransform parameter from PaintFilteredFrame. r=mstange There are two callers of nsFilterInstance::PaintFilteredFrame: 1. nsSVGUtils::PaintFrameWithEffects at [1] This function is used while painting a filtered element on a path which display item painting is not supported yet, such as drawing elements inside a indirect painted SVG object, such as a mask, a clipPath or a gradient object. Let's say we have a masked element, which refers to an SVG mask, and there is a filtered element inside that SVG mask. Using nsFilterInstance::PaintFilteredFrame to paint that filtered frame in the mask, we have to pass a gfxContext and a transform matrix to it. The transform of the gfxContext 'target' that we pass in consists of a transform from the referenced frame, of the masked frame, to the masked frame. We also pass in a transform matrix 'aTransform', this matrix contains a transform from the the masked frame to the filtered frame in *device units*, which means it contains css-to-dev-px scaling factor. 2. nsSVGIntegrationUtils::PaintFilter at [2] This function is used by normal display item painting. The same, we pass a gfxContext 'context' and a transform matrix 'tm' into nsFilterInstance::PaintFilteredFrame. The transform matrix of 'context' consists of a transform from the referenced frame, of the filtered frame, to this filtered frame, but the scale factor was taken out . The transform matrix 'tm' we pass in contains scale transform from the referenced frame to the filtered frame in *device unit*. Inside nsFilterInstance::PaintFilteredFrame, we treat the transform matrix of 'aCtx' and 'aTransform' as parameters we pass in in #2 caller. So it can be failed in #1. For example, if the filtered frame inside a masked frame has a translation transform applied, since that translation was put in 'aTransfrom', but we only use the scale factor of 'aTransform' in nsFilterInstance::PaintFilteredFrame, translation factor disappears. In this patch, I unified the definition of parameters of nsFilterInstance::PaintFilteredFrame: 1. nsFilterInstance::PaintFilteredFrame(aCtx): the transform matrix of aCtx should be a transform from the referenced frame to the filtered frame in *css units*. Originally, the aCtx we passed in #1 is in device units, which should be fixed; the aCtx we passed in #2 does not even include css scaling factor, need be fixed too. 2. nsFilterInstance::PaintFilteredFrame(aTransform): this transform matrix should contain only scaling factor in device units. And I removed it in the end since I found we can get this value easily right inside the callee. [1] https://hg.mozilla.org/mozilla-central/file/ef585ac7c476/layout/svg/nsSVGUtils.cpp#l857 [2] https://hg.mozilla.org/mozilla-central/file/ef585ac7c476/layout/svg/nsSVGIntegrationUtils.cpp#l1114 MozReview-Commit-ID: gRV128NyQv
45278d597320c6f107d21fcff591a5bac7c42a46: Bug 1385239 - Part 1. Pass gfxContext, instead of DrawTarget, into nsFilterInstance::PaintFilteredFrame. r=mstange
cku <cku@mozilla.com> - Fri, 25 Aug 2017 16:33:33 +0800 - rev 662792
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1385239 - Part 1. Pass gfxContext, instead of DrawTarget, into nsFilterInstance::PaintFilteredFrame. r=mstange This change makes the next patch free of doing Matrix to gfxMatrix conversion. MozReview-Commit-ID: 8K9RNgjZPTw
2dc8bf7c38ae8f44a99b0ccfc342bb50abd9d93f: Bug 1380980 - stylo: Add test; r=emilio
Manish Goregaokar <manishearth@gmail.com> - Sat, 09 Sep 2017 01:17:49 -0700 - rev 662791
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1380980 - stylo: Add test; r=emilio MozReview-Commit-ID: JLk5H1j2v89
bf6b321ede7ba707a4a6ab47d72cdf5824f8e04f: Bug 1380980 - stylo: Add (unused) absolute offset to FontComputationData; r=emilio
Manish Goregaokar <manishearth@gmail.com> - Fri, 08 Sep 2017 15:25:44 -0700 - rev 662790
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1380980 - stylo: Add (unused) absolute offset to FontComputationData; r=emilio MozReview-Commit-ID: EqtIs2NDm5g
99f47bca403abe52ae7fa7905a4455cc474350a1: Backed out 2 changesets (bug 1397123) for Android build bustage
Phil Ringnalda <philringnalda@gmail.com> - Mon, 11 Sep 2017 20:23:22 -0700 - rev 662789
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Backed out 2 changesets (bug 1397123) for Android build bustage Backed out changeset 803c2d6f4be4 (bug 1397123) Backed out changeset 2d41a6eb4df4 (bug 1397123) MozReview-Commit-ID: A45nVCrhbQA
fe7465d53091ebfd694e16620c90406e56f193b5: Backed out 4 changesets (bug 1398601) for Windows Marionette crashes @ ExecuteInExtensibleLexicalEnvironment
Phil Ringnalda <philringnalda@gmail.com> - Mon, 11 Sep 2017 20:20:16 -0700 - rev 662788
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Backed out 4 changesets (bug 1398601) for Windows Marionette crashes @ ExecuteInExtensibleLexicalEnvironment Backed out changeset 7aac2595bc17 (bug 1398601) Backed out changeset 7a4bb5a1848a (bug 1398601) Backed out changeset dd4af7998505 (bug 1398601) Backed out changeset e9816be61b49 (bug 1398601) MozReview-Commit-ID: LLJ99dkRQEg
f008f172724b09ea688befab887d51bdec9aea1f: servo: Merge #18451 - stylo: Add support for calcs in base size calculation (from Manishearth:stylo-calc-fontsize); r=emilio
Manish Goregaokar <manishearth@gmail.com> - Mon, 11 Sep 2017 21:01:57 -0500 - rev 662787
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
servo: Merge #18451 - stylo: Add support for calcs in base size calculation (from Manishearth:stylo-calc-fontsize); r=emilio This tracks an offset along with the ratio for the keyword font size data. The offset gets used when a calc is involved whilst inheriting font-size (it is the computed value of that calc ignoring em/percentage portions, which go into the ratio). If the family or language changes, the new font size can be computed by taking the keyword's size in the context of that family/language, multiplying it by the ratio, and adding the offset. r=emilio https://bugzilla.mozilla.org/show_bug.cgi?id=1380980 Source-Repo: https://github.com/servo/servo Source-Revision: f91ea02bf7336653d7fd6c7833b7fd5fcd7b9fac
803c2d6f4be4338451dea50c54508c3b7662b8e0: Bug 1397123 - [Part2] Decouple ChromiumCDMProxy from ChromiumCDMParent. r=cpearce
James Cheng <jacheng@mozilla.com> - Mon, 11 Sep 2017 12:17:36 +0800 - rev 662786
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1397123 - [Part2] Decouple ChromiumCDMProxy from ChromiumCDMParent. r=cpearce 1. Pass ChromiumCDMCallback interface to ChromiumCDMParent instead of ChromiumCDMProxy directly. 2. Wrap dispatching to main thread function to clean up the redundant code. MozReview-Commit-ID: 5HxS9Fc1yr
2d41a6eb4df42ff4d082e8151987da031fa38849: Bug 1397123 - [Part1] Make aMessage of CDMProxy::OnSessionMessage const. r=cpearce
James Cheng <jacheng@mozilla.com> - Mon, 11 Sep 2017 12:16:18 +0800 - rev 662785
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1397123 - [Part1] Make aMessage of CDMProxy::OnSessionMessage const. r=cpearce MozReview-Commit-ID: Bsw6s2HE02
ad12f05d2416bd49ab0af66370c442a7ed563214: Bug 1334582 - Check whether overall progress exceeds UINT64_MAX. r=boris
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 12 Sep 2017 08:42:54 +0900 - rev 662784
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1334582 - Check whether overall progress exceeds UINT64_MAX. r=boris The overall progress is factored in iteration start, so even if TimingParams.mIterations is less than UINT64_MAX, it will exceed UINT64_MAX. MozReview-Commit-ID: CEOYAGsCoIE
1daf0a6213e69fd191b324448cb53bbc09fd6ef6: Bug 1334582 - Use UINT64_MAX instead of IsInfinite() for checking whether TimingParans.mIterations is infinite or not. r=boris
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 12 Sep 2017 08:42:45 +0900 - rev 662783
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1334582 - Use UINT64_MAX instead of IsInfinite() for checking whether TimingParans.mIterations is infinite or not. r=boris Because our ComputedTiming.mCurrentIteration is uint64_t. MozReview-Commit-ID: FjbhEvTUMr4
8d5aba559d564dee65d5fe28091bfdfd661cf25a: Bug 1398628 - Remove VIDEO_CDM_CREATED telemetry and the related code. r=cpearce,francois
James Cheng <jacheng@mozilla.com> - Mon, 11 Sep 2017 11:51:12 +0800 - rev 662782
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1398628 - Remove VIDEO_CDM_CREATED telemetry and the related code. r=cpearce,francois MozReview-Commit-ID: 3xDiz9S90bY
d2d647e40002272e255ef95934e1d44b8aaa29b6: servo: Merge #18447 - Remove most uses of ComputedValueAsSpecified (from servo:kill-cvas); r=emilio
Anthony Ramine <n.oxyde@gmail.com> - Mon, 11 Sep 2017 20:04:12 -0500 - rev 662781
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
servo: Merge #18447 - Remove most uses of ComputedValueAsSpecified (from servo:kill-cvas); r=emilio Source-Repo: https://github.com/servo/servo Source-Revision: 5cc2b4f705e420b156899ed55072ccc11d0e50c0
9584975d84e0f443d83828be340b92391bf68377: Bug 1381126: Resume requiring WebAuthn RP ID to be a Domain String r=keeler
J.C. Jones <jjones@mozilla.com> - Mon, 11 Sep 2017 09:06:28 -0700 - rev 662780
Push 79191 by bmo:mh+mozilla@glandium.org at Tue, 12 Sep 2017 04:11:54 +0000
Bug 1381126: Resume requiring WebAuthn RP ID to be a Domain String r=keeler In Bug 1380421 we reverted some behavior that required Web Authentication's RP ID to be domain string to permit it to be an origin, too, for interop testing. That is no longer needed, so this patch resumes enforcement that RP ID be a domain string. It also adds a needed test that the RP ID hash is calculated correctly. MozReview-Commit-ID: 8dDjzo5kQKP
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip