17fca44728967a6dda307a2640bbd3d479d04302: Bug 1413540 - Merge 'flash' filter into 'Others'. r=Honza draft
abhinav <abhinav.koppula@gmail.com> - Sun, 05 Nov 2017 12:26:36 +0530 - rev 693296
Push 87746 by bmo:abhinav.koppula@gmail.com at Sun, 05 Nov 2017 06:57:01 +0000
Bug 1413540 - Merge 'flash' filter into 'Others'. r=Honza MozReview-Commit-ID: CjxepUwYHr0
730050c818f4aa3ff56a2bf5e4a537cc180efeed: Don't remove the front buffer when creating a new buffer (bug 1399692 part 9, r?bas) draft
Ryan Hunt <rhunt@eqrion.net> - Sun, 05 Nov 2017 01:17:01 -0500 - rev 693295
Push 87745 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:43:35 +0000
Don't remove the front buffer when creating a new buffer (bug 1399692 part 9, r?bas) Clear will remove the current front buffer if there is one. Doing this whenever we create a back buffer will cause us to always need to create a back buffer, as after we swap we won't have a back buffer. MozReview-Commit-ID: Ip9sAO7LQwf
eaa8864b72f4ae466c10c60a30e1d0dc070c4292: Don't copy over regions that will be painted in this frame (bug 1399692 part 8, r?bas) draft
Ryan Hunt <rhunt@eqrion.net> - Sat, 04 Nov 2017 14:52:31 -0400 - rev 693294
Push 87745 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:43:35 +0000
Don't copy over regions that will be painted in this frame (bug 1399692 part 8, r?bas) We do the same in FinalizeFrame, so we should do it here. MozReview-Commit-ID: JTKDj8yrtI2
deccbd0f9742b702170dda801365397a6017caaf: Don't remove the front buffer when creating a new buffer (bug 1399692 part 9, r?bas) draft
Ryan Hunt <rhunt@eqrion.net> - Sun, 05 Nov 2017 01:17:01 -0500 - rev 693293
Push 87744 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:31:51 +0000
Don't remove the front buffer when creating a new buffer (bug 1399692 part 9, r?bas) MozReview-Commit-ID: Ip9sAO7LQwf
a88b6016e800801b9152c7fde5638fb80016288f: Don't copy over regions that will be painted in this frame (bug 1399692 part 8, r?bas) draft
Ryan Hunt <rhunt@eqrion.net> - Sat, 04 Nov 2017 14:52:31 -0400 - rev 693292
Push 87744 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:31:51 +0000
Don't copy over regions that will be painted in this frame (bug 1399692 part 8, r?bas) MozReview-Commit-ID: JTKDj8yrtI2
f57a91fdc56f00bc03ee86160975a689d66ca59c: Replay buffer commands on paint thread when OMTP is enabled (bug 1399692 part 7, r=bas) draft
Ryan Hunt <rhunt@eqrion.net> - Thu, 26 Oct 2017 00:47:17 -0400 - rev 693291
Push 87744 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:31:51 +0000
Replay buffer commands on paint thread when OMTP is enabled (bug 1399692 part 7, r=bas) This commit does the work of actually dispatching the recorded buffer operations to the paint thread, and removing some main thread asserts from TextureClient. MozReview-Commit-ID: CN3RoQPz9fP
bef5f8dbb66bf2d713338b93aca8508ab6376b0f: Record buffer operations to a struct for replaying on paint thread (bug 1399692 part 6, r=bas) draft
Ryan Hunt <rhunt@eqrion.net> - Wed, 25 Oct 2017 10:20:49 -0400 - rev 693290
Push 87744 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:31:51 +0000
Record buffer operations to a struct for replaying on paint thread (bug 1399692 part 6, r=bas) This commit adds a CapturedBufferState which is used to record all the operations that are necessary for preparing the buffers. The commands are then instantly executed to preserve the same behavior, but in the following commit they will be dispatched to the paint thread. Note: RotatedBuffer's aren't thread safe and so a shallow copy needs to be made for sending to the paint thread. This complicates the code for AdjustTo as it can fail naturally and the buffer parameter changes are needed later in BeginPaint. So the code for AdjustTo is split up a bit to accomodate that. MozReview-Commit-ID: FwSwFay887o
7e4bdcc99d568408280c686944cbc36ad33bfa2a: Simplify copying the front buffer to the back buffer (bug 1399692 part 5, r=bas) draft
Ryan Hunt <rhunt@eqrion.net> - Mon, 23 Oct 2017 18:27:53 -0400 - rev 693289
Push 87744 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:31:51 +0000
Simplify copying the front buffer to the back buffer (bug 1399692 part 5, r=bas) To sync the back buffer with the front buffer, we set the back buffer rect and rotation to the front buffer's, and then copy over the pixels that different. We used to do the updating of the rect and rotation before BeginPaint, but that isn't necessary and we can move it to be with the copying of pixels. MozReview-Commit-ID: HzBKvMZkn1
0dc932c732807659af8dfe418511c57f2c05fa91: Don't create back buffer for front buffer until we know what type to create. (bug 1399692 part 4, r=bas) draft
Ryan Hunt <rhunt@eqrion.net> - Mon, 23 Oct 2017 15:33:40 -0400 - rev 693288
Push 87744 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:31:51 +0000
Don't create back buffer for front buffer until we know what type to create. (bug 1399692 part 4, r=bas) This commit is an optimization for double buffering that delays the creation of a back buffer until we know what kind of content type it needs to be. Before this commit, we would EnsureBackBufferIfFrontBuffer before BeginPaint, then in BeginPaint we could determine that we actually needed a different kind of buffer because the content changed type, and recreate it. This was needed because BeginPaint would copy the old front buffer to the buffer created by EnsureBackBufferIfFrontBuffer, and then if anything failed or we had determined we couldn't reuse the buffer, we would create a new one and copy that "temporary" back buffer over, and use the new one. This is unnecessary because we only need read access on that "temporary" back buffer, and so we can just use the current front buffer instead. This optimization only affects the double buffered case, and the single buffered or basic cases should remain the same. Note: Because we now need the front buffer for copying into the new back buffer, we cannot Clear() it away in some error cases. MozReview-Commit-ID: 2hyrrUhA4zO
cf9cb92b211018158ac884c3c5441929a077a5c7: Remove BufferContentType and add ValidBufferSize (bug 1399692 part 3, r=bas) draft
Ryan Hunt <rhunt@eqrion.net> - Mon, 23 Oct 2017 14:56:13 -0400 - rev 693287
Push 87744 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:31:51 +0000
Remove BufferContentType and add ValidBufferSize (bug 1399692 part 3, r=bas) BufferContentType and BufferSizeOkFor make more sense as general functions for any RotatedBuffer, and this helps out in a later patch. MozReview-Commit-ID: EAVodvl4WTu
c33307deab28e10682754c862eae638ede7275cc: Simplify the code for creating a new back buffer (bug 1399692 part 2, r=bas) draft
Ryan Hunt <rhunt@eqrion.net> - Mon, 23 Oct 2017 12:40:01 -0400 - rev 693286
Push 87744 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:31:51 +0000
Simplify the code for creating a new back buffer (bug 1399692 part 2, r=bas) MozReview-Commit-ID: D28JNYWD9Uc
5671ddc670c28e3feea352387f57f99f1ed39bab: Remove unneeded lambda capture in paint thread (bug 1399692 part 1, r=bas) draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 31 Oct 2017 01:55:24 -0400 - rev 693285
Push 87744 by bmo:rhunt@eqrion.net at Sun, 05 Nov 2017 06:31:51 +0000
Remove unneeded lambda capture in paint thread (bug 1399692 part 1, r=bas) MozReview-Commit-ID: 71X22PHRTRz
545f710bc4d420594c1c0a6131fd02d3a7827136: Bug 1410416 - Part 2 - Add test cases about removing service workers, r?baku draft
Fischer.json <fischer.json@gmail.com> - Wed, 01 Nov 2017 13:43:58 +0800 - rev 693284
Push 87743 by bmo:fliu@mozilla.com at Sun, 05 Nov 2017 05:32:00 +0000
Bug 1410416 - Part 2 - Add test cases about removing service workers, r?baku MozReview-Commit-ID: 6MeilGCkomc
a7f1520e1dc96d1175f50ef9077012c23bd9c036: Bug 1410416 - Part 1: Have SiteDateManager.jsm call `propagateUnregister` to remove service workers, r?baku draft
Fischer.json <fischer.json@gmail.com> - Fri, 20 Oct 2017 21:35:58 +0800 - rev 693283
Push 87743 by bmo:fliu@mozilla.com at Sun, 05 Nov 2017 05:32:00 +0000
Bug 1410416 - Part 1: Have SiteDateManager.jsm call `propagateUnregister` to remove service workers, r?baku MozReview-Commit-ID: BNUhm6a2x1b
5b9392666ec8918ca1e205257c37922c509a301f: Bug 1403348: Part 4 - Annotate certain startup crashes with AsyncShutdown script contents. r?mccr8 data-r?rweiss draft
Kris Maglione <maglione.k@gmail.com> - Sat, 04 Nov 2017 17:20:17 -0700 - rev 693282
Push 87742 by maglione.k@gmail.com at Sun, 05 Nov 2017 00:25:24 +0000
Bug 1403348: Part 4 - Annotate certain startup crashes with AsyncShutdown script contents. r?mccr8 data-r?rweiss We're seeing startup crashes which point to data corruption in the source of the AsyncShutdown component and module, but it's unclear whether the source of this corruption is on disk, in memory, or in XDR data. This change annotates crash reports with the contents of those files, so that we can compare the actual source with the corrupted values in the generated errors, and narrow down the source of the corruption. MozReview-Commit-ID: 7p8y73XUGLK
317ab799abbbfea73b0ac54cc92fb39745e695a7: Bug 1408544 - part 2: RangeBoundaryBase shouldn't compute mRef when mOffset is specified r?mystor draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 02 Nov 2017 21:25:14 +0900 - rev 693281
Push 87741 by masayuki@d-toybox.com at Sun, 05 Nov 2017 00:25:13 +0000
Bug 1408544 - part 2: RangeBoundaryBase shouldn't compute mRef when mOffset is specified r?mystor RangeBoundaryBase shouldn't compute mRef when it's initialized with offset. E.g., some users of the template class may initialize it with a container and offset in it but it may not refer mRef or may refer after modifying offset. On the other hand, RangeBoundaryBase::InvalidateOffset() is a special method. It assumes that mRef is always initialized when it's called but can be invalidate mOffset until retrieved actually. This is necessary for nsRange::mStart and nsRange::mEnd since the offset may be changed when some nodes are inserted before the referring node. So, now, InvalidateOffset() should be a protected method and make nsRange a friend class of RangeBoundaryBase. Then, when nsRange sets mStart and/or mEnd, nsRange itself should guarantee that their mRefs are initialized. MozReview-Commit-ID: Alr4YkDXIND
af027d3a803c2f1b8cb3a57b5489fc96b3d675fb: Bug 1408544 - part 1: Reimplement EditorDOMPoint as a subclass of RangeBoundary r?m_kato, mystor draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 01 Nov 2017 14:41:03 +0900 - rev 693280
Push 87741 by masayuki@d-toybox.com at Sun, 05 Nov 2017 00:25:13 +0000
Bug 1408544 - part 1: Reimplement EditorDOMPoint as a subclass of RangeBoundary r?m_kato, mystor A lot of methods in editor returns a child offset with an out param when it returns its container and offset in the container. This is ugly hack for performance of nsINode::IndexOf(). However, there are a lot of regression since the relation between offset and child node can be broken really easily. So, we should make EditorDOMPoint as a subclass of RangeBoundary and manage a set of container, reference child and its offset in it (e.g., SetNextSibling() added by this patch). Note that RangeBoundary's performance is not good for temporary use if we set a point with offset, it immediately retrieves mRef. The following patch will improve this performance. MozReview-Commit-ID: 7mcJ1P1OjVr
e7fee7042d971d73c0e5caafba3b8d15da1bc8ca: merge mozilla-inbound to mozilla-central. r=merge a=merge
Sebastian Hengst <archaeopteryx@coole-files.de> - Sat, 04 Nov 2017 22:55:41 +0100 - rev 693279
Push 87741 by masayuki@d-toybox.com at Sun, 05 Nov 2017 00:25:13 +0000
merge mozilla-inbound to mozilla-central. r=merge a=merge MozReview-Commit-ID: DEsdO0kjfDL
bfd94ce6cddd5977e8151437dd0ac755fd5d7775: merge mozilla-central to mozilla-inbound. r=merge a=merge on a CLOSED TREE
Sebastian Hengst <archaeopteryx@coole-files.de> - Sat, 04 Nov 2017 17:41:04 +0100 - rev 693278
Push 87741 by masayuki@d-toybox.com at Sun, 05 Nov 2017 00:25:13 +0000
merge mozilla-central to mozilla-inbound. r=merge a=merge on a CLOSED TREE
1ce74c61c5c3355689b65ca7453020e90897ee00: Bug 1413143: Make font inflation computation less lazy. r=bz,JanH
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 01 Nov 2017 11:24:17 +0100 - rev 693277
Push 87741 by masayuki@d-toybox.com at Sun, 05 Nov 2017 00:25:13 +0000
Bug 1413143: Make font inflation computation less lazy. r=bz,JanH This makes it a bit more straight-forward to change the system font scale, preserving the sync MediaFeatureChanged event. This also avoids notifying media queries when the shell is not initialized. In particular, the patch in bug 1404545 allows calling MediaFeatureValuesChanged on a still-initializing pres-shell. This is nasty, and all this initialization order is kind of a mess, but I'm not reworking it for now... Also, this drops the invalidation of font-inflation when a doctype is added to the document. GetViewportInfo() already relies on the doctype not changing, as noted in a comment. MozReview-Commit-ID: Knw7dM1B04Y
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip