4d23f192ffe345cf60527325bb56bc7d4f27c4a4: Bug 1464865: Some trivial cleanup. r=xidorn
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 29 May 2018 13:03:54 +0200 - rev 420289
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1464865: Some trivial cleanup. r=xidorn MozReview-Commit-ID: 8ClaBR9ooGb
09d9ee3fe4bbe37634ead56e93241e761326af89: Bug 1464865: Don't let @namespace rules that aren't going to be inserted affect the namespace map. r=xidorn
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 28 May 2018 23:56:20 +0200 - rev 420288
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1464865: Don't let @namespace rules that aren't going to be inserted affect the namespace map. r=xidorn MozReview-Commit-ID: 9bjlEBExqsr
1268d562bda02ec1084c64679ec201783b07c218: Bug 1464472. r=jandem
Jeff Walden <jwalden@mit.edu> - Sat, 26 May 2018 03:07:36 -0700 - rev 420287
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1464472. r=jandem
cc3808652819da4c418d55a63f194d211111736e: Bug 1435828 - Reimport test262 tests with the json-superset tests not disabled. r=anba
Jeff Walden <jwalden@mit.edu> - Fri, 25 May 2018 15:41:05 -0700 - rev 420286
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1435828 - Reimport test262 tests with the json-superset tests not disabled. r=anba
1a85fc556cd30b3f5c16fc33f595aeacb5abd11a: Bug 1435828 - Allow U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR, encoding those literal code points, inside string literals. r=anba
Jeff Walden <jwalden@mit.edu> - Fri, 25 May 2018 15:40:30 -0700 - rev 420285
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1435828 - Allow U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR, encoding those literal code points, inside string literals. r=anba
3f2802f1c53991189b9379270a03f3ed8f46af9b: Bug 1464486 - Update Debugger Frontend v59. r=dwalsh
Jason Laster <jason.laster.11@gmail.com> - Fri, 25 May 2018 13:52:20 -0400 - rev 420284
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1464486 - Update Debugger Frontend v59. r=dwalsh
dfbe62f4ab7535c1388586e309bd01e339ef3142: Backed out 1 changesets (bug 1462836) for "Test harness output was not a valid structured log message" on a CLOSED TREE
shindli <shindli@mozilla.com> - Tue, 29 May 2018 15:59:40 +0300 - rev 420283
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Backed out 1 changesets (bug 1462836) for "Test harness output was not a valid structured log message" on a CLOSED TREE Backed out changeset f469e464de5f (bug 1462836)
9b516954e1031202b00b924accfb0861a973986f: Bug 1462355 - Part 9. Lock animated imgFrame objects at creation rather than deferring. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:13 -0400 - rev 420282
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 9. Lock animated imgFrame objects at creation rather than deferring. r=tnikkel
8d412f560489b690870257077e15f1b1ad3d7b75: Bug 1462355 - Part 8. Avoid allocating on the heap in DrawableFrameRef. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:13 -0400 - rev 420281
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 8. Avoid allocating on the heap in DrawableFrameRef. r=tnikkel We can easily use Maybe<DataSourceSurface::ScopedMap> instead of allocated the map on the heap. This does require some minor changes to ScopedMap to properly support moves, but should be much more efficient.
baeab7da1768fb4741c1ee8942a04e70340fc3b4: Bug 1462355 - Part 7. Don't hit the SurfaceCache in FrameAnimator::GetCompositedFrame if possible. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:13 -0400 - rev 420280
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 7. Don't hit the SurfaceCache in FrameAnimator::GetCompositedFrame if possible. r=tnikkel In FrameAnimator::GetCompositedFrame, we call SurfaceCache::Lookup even when we use the composited frame directly and leave the lookup result unused. The only value in performing the lookup could be to mark the surface as used to avoid expiring it too soon, but FrameAnimator::RequestRefresh should already be doing enough to keep it alive, if the image isn't locked in the first place.
a7331d229cc8add978906ccc5582795bceb58d81: Bug 1462355 - Part 6. Reuse RawAccessFrameRef in FrameAnimator where possible. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:12 -0400 - rev 420279
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 6. Reuse RawAccessFrameRef in FrameAnimator where possible. r=tnikkel In FrameAnimator::RequestRefresh and AdvanceFrame, we currently create several RawAccessFrameRef objects to the same frames, either to get timeouts or perform the blending. With some tweaking, we can avoid requesting the same frame more than once. This will avoid mutex locks on the surface provider and the frame itself.
c67a6f1315b49a4faeec778709ab0d3a956a57dd: Bug 1462355 - Part 5. Avoid converting from DrawableFrameRef to RawAccessFrameRef. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:12 -0400 - rev 420278
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 5. Avoid converting from DrawableFrameRef to RawAccessFrameRef. r=tnikkel DrawableSurface only exposes DrawableFrameRef to its users. This is sufficient for the drawing related code in general, but FrameAnimator really needs RawAccessFrameRef to the underlying pixel data (which may be paletted). While one can get a RawAccessFrameRef from a DrawableFrameRef, it requires yet another lock of the imgFrame's mutex. We can avoid this extra lock if we just allow the callers to get the right data type in the first place.
93bdeed04a6b61139bc1c1b12088dafc260b3599: Bug 1462355 - Part 4. Remove imgFrame::GetAnimationData as it is no longer used. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:12 -0400 - rev 420277
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 4. Remove imgFrame::GetAnimationData as it is no longer used. r=tnikkel
45406c2b9e9cfa9fc2dd8cd80a35c82cf9480efc: Bug 1462355 - Part 3. Make FrameAnimator use the new imgFrame/RawAccessFrameRef methods. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:12 -0400 - rev 420276
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 3. Make FrameAnimator use the new imgFrame/RawAccessFrameRef methods. r=tnikkel
3ea8add8bacc5b2b74b03ff3ba410211000c76c5: Bug 1462355 - Part 2. Expose imgFrame's data pointers via RawAccessFrameRef. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:12 -0400 - rev 420275
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 2. Expose imgFrame's data pointers via RawAccessFrameRef. r=tnikkel RawAccessFrameRef ensures there is a valid data pointer to the pixel data for the frame. It is a common pattern for users of RawAccessFrameRef to follow up with a request for the data pointer shortly after creation. We can avoid an extra lock by exposing this data pointer from RawAccessFrameRef, and populating it via imgFrame::LockImageData.
eb8ec97c5f5fa8555c8c9370b029807a707fc15f: Bug 1462355 - Part 1c. Make individual image decoders to use updated Decoder/SurfacePipe methods. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:12 -0400 - rev 420274
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 1c. Make individual image decoders to use updated Decoder/SurfacePipe methods. r=tnikkel
87a0a6e103d8151d0e40929580545e3fbcc6b490: Bug 1462355 - Part 1b. Update Decoder and SurfacePipe plumbing to use updated imgFrame methods. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:12 -0400 - rev 420273
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 1b. Update Decoder and SurfacePipe plumbing to use updated imgFrame methods. r=tnikkel
259ee94de92ca9c586cfa02cb92db331aace64d1: Bug 1462355 - Part 1a. Make imgFrame animation parameters threadsafe. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 29 May 2018 08:36:11 -0400 - rev 420272
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1462355 - Part 1a. Make imgFrame animation parameters threadsafe. r=tnikkel We currently choose to set the animation parameters (blend method, blend rect, disposal method, timeout) in imgFrame::Finish instead of imgFrame::InitForDecoder. The decoders themselves already have access to the necessary information at the time InitForDecoder is called, so there is no reason to do this. Moving the configuration to initialization will allow us to relax the mutex protection on these parameters. This part simply reorganizes imgFrame, and subsequent parts will introduce the necessary changes to SurfacePipe and decoders.
516dc753d6541dd3179a3627b44dd5209b053301: Bug 1465039 - Rename Array.prototype.flatten to Array.prototype.flat. r=anba
Tom Schuster <evilpies@gmail.com> - Tue, 29 May 2018 13:23:06 +0200 - rev 420271
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1465039 - Rename Array.prototype.flatten to Array.prototype.flat. r=anba
e44345b44d4e1e4f94d066bd314597da3905c6c9: Bug 1465039 - Update test262. r=anba
Tom Schuster <evilpies@gmail.com> - Tue, 29 May 2018 13:22:30 +0200 - rev 420270
Push 34069 by nerli@mozilla.com at Tue, 29 May 2018 21:42:06 +0000
Bug 1465039 - Update test262. r=anba
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip