e51308ef7c09f6dcf47f614f91bb3eef23f2fe2b: Bug 1367696 - PART II add xpcshell structure for onboarding;r=mossop draft
gasolin <gasolin@gmail.com> - Thu, 22 Jun 2017 16:25:53 +0800 - rev 600859
Push 65887 by bmo:gasolin@mozilla.com at Tue, 27 Jun 2017 21:31:43 +0000
Bug 1367696 - PART II add xpcshell structure for onboarding;r=mossop MozReview-Commit-ID: LA3LD8qx35d
dd52d8b55b6ad1ab27c9c88e1c4be2b2ec61b873: Bug 1367696 - PART I determine the tour type;r=mossop, timdream draft
gasolin <gasolin@gmail.com> - Thu, 22 Jun 2017 16:10:46 +0800 - rev 600858
Push 65887 by bmo:gasolin@mozilla.com at Tue, 27 Jun 2017 21:31:43 +0000
Bug 1367696 - PART I determine the tour type;r=mossop, timdream MozReview-Commit-ID: KUXPftqZdl1
36bf9358f59ca972626c5c28e37e1ce5c145fc5b: Bug 1376550 - Make OSX complete.mar's generated via ./mach repackage mozharness configs r=aki draft
Justin Wood <Callek@gmail.com> - Tue, 27 Jun 2017 14:26:16 -0700 - rev 600857
Push 65886 by Callek@gmail.com at Tue, 27 Jun 2017 21:26:52 +0000
Bug 1376550 - Make OSX complete.mar's generated via ./mach repackage mozharness configs r=aki Support OSX Signed nightlies (in the complete.mar too) MozReview-Commit-ID: 6iPrPhjj34g
60247174d73362da11d71c6777bd89d704598584: Bug 1372056: Test for dynamic text-decoration propagation. r?xidorn draft
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 27 Jun 2017 14:22:14 -0700 - rev 600856
Push 65885 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:25:35 +0000
Bug 1372056: Test for dynamic text-decoration propagation. r?xidorn MozReview-Commit-ID: ArB3uZmzhwn
e05d7ab964bd27f1934ad22bd91fa87b753457df: Bug 1372056: Test for dynamic text-decoration propagation. r?xidorn draft
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 27 Jun 2017 14:22:14 -0700 - rev 600855
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1372056: Test for dynamic text-decoration propagation. r?xidorn MozReview-Commit-ID: ArB3uZmzhwn
796f1a1e0e2c23135e24591553f497a68f889987: style: Fix propagation of text-decoration lines. draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 26 Jun 2017 15:30:13 -0700 - rev 600854
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
style: Fix propagation of text-decoration lines. Signed-off-by: Emilio Cobos Álvarez <emilio@crisal.io>
ae95232c86e42765592779327aeff0f83261bedc: style: Cleanup duplicated code in the definition of ComputedValues. draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 26 Jun 2017 15:19:18 -0700 - rev 600853
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
style: Cleanup duplicated code in the definition of ComputedValues. Signed-off-by: Emilio Cobos Álvarez <emilio@crisal.io>
e4b1fde6db29e8a3991d6cbc0c91d0e02430671b: style: Add some flags to the computed values. draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 26 Jun 2017 22:50:43 +0200 - rev 600852
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
style: Add some flags to the computed values. This will allow us to fix propagation of text-decoration, and also to implement inlinization of ruby kids. Signed-off-by: Emilio Cobos Álvarez <emilio@crisal.io>
28f0767167d66423db8a42280ffed67270d05e1f: Bug 1376158: Don't let non-primary frames affect the mIncrementScriptLevel of the content. r?xidorn draft
Emilio Cobos Álvarez <emilio@crisal.io> - Sun, 25 Jun 2017 21:26:49 +0200 - rev 600851
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1376158: Don't let non-primary frames affect the mIncrementScriptLevel of the content. r?xidorn In the test-case we have a munderoverFrame setting the script-level of the content through a frame which is an anonymous block, and another one setting the script level to the opposite for the same content, via its primary frame. That's somewhat silly, and with the previous patches the non-primary one happened to be ignored because the IncrementScriptLevel flag was set on the fly. The whole situation is somewhat silly, because as far as I can tell MathML tries to map one frame to one element, and this doesn't hold. This patch makes the behavior consistent and makes the test-case render as "invalid markup", which is what should happen anyway. MozReview-Commit-ID: 5ugxVwX3sMa
4fdf1ba21f3cce03954e1e580e0665213595e4a3: No hover generation draft
Emilio Cobos Álvarez <emilio@crisal.io> - Sat, 24 Jun 2017 11:43:30 +0200 - rev 600850
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
No hover generation MozReview-Commit-ID: 2n9HKg8Vi5P
c54c24135d43fa6c2bab702f266ea1712fd00501: Bug 1375674: Reftest for the display: contents issue. r?heycam draft
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 23 Jun 2017 19:41:23 +0200 - rev 600849
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1375674: Reftest for the display: contents issue. r?heycam MozReview-Commit-ID: Kca1oIzo7oZ
534d67f98451191c986bd733ef655bed3db0904f: Bug 1375674: Track the owner that represents the changes handled, and fix a bunch of issues while at it. r?heycam draft
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 23 Jun 2017 19:31:35 +0200 - rev 600848
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1375674: Track the owner that represents the changes handled, and fix a bunch of issues while at it. r?heycam In particular, this fixes: * Restyling of <area> elements that reuse the primary frame mapping for the image map. * Restyling of children of display: contents elements when the display: contents element generates a hint. * Restyling of out-of-flows (if my analysis in the bug is right). * Restyling of the ::backdrop pseudo-element. * Restyling of the Viewport frame. I only managed to do a reftest for the second one, but the rest of them are covered by the assertions added. MozReview-Commit-ID: E7QtiQ1vPqu
f5eb775665526290636fefa4c6b68d354e64c036: Bug 1375674: Don't use the table change hints for the table wrapper frame. r?heycam draft
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 23 Jun 2017 19:30:16 +0200 - rev 600847
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1375674: Don't use the table change hints for the table wrapper frame. r?heycam MozReview-Commit-ID: 7Qe07N6zvIt
057b7d08d620d6efa05ff356068e4b170197a9a1: Bug 1375674: Don't use the owner's changes handled for the backdrop frame. r?heycam draft
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 23 Jun 2017 19:26:20 +0200 - rev 600846
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1375674: Don't use the owner's changes handled for the backdrop frame. r?heycam MozReview-Commit-ID: GpIQwqge8L
3267048797f00c385174667252024e5af2fdeb49: Bug 1375674: Constify and simplify nsLayoutUtils::{First,Last}ContinuationOrIBSplitSibling. r?heycam draft
Emilio Cobos Álvarez <emilio@crisal.io> - Sun, 25 Jun 2017 01:48:27 +0200 - rev 600845
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1375674: Constify and simplify nsLayoutUtils::{First,Last}ContinuationOrIBSplitSibling. r?heycam MozReview-Commit-ID: phsCyamDum
11e88910799fbc309ab41d54eebbaca2a5b991a1: Bug 1376449 - Robustify startDrawing to prevent calling callback function after stop() has been called. r=pehrsons
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 27 Jun 2017 13:55:45 -0400 - rev 600844
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1376449 - Robustify startDrawing to prevent calling callback function after stop() has been called. r=pehrsons MozReview-Commit-ID: 5vPtTHBGJhN
d6f8d347f25e05022f5cf086f137c8747d68c124: Bug 1374037 - catch shared memory exceptions to prevent crash. r=esawin
John Lin <jolin@mozilla.com> - Wed, 21 Jun 2017 15:44:43 +0900 - rev 600843
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1374037 - catch shared memory exceptions to prevent crash. r=esawin MozReview-Commit-ID: CubvyqLxmXb
e6dfe16f777b4363fd4c4f76e5a9022dfe357ab5: Bug 1357715 - Skip DevTools tests on Stylo that use shadow DOM. r=heycam
J. Ryan Stinnett <jryans@gmail.com> - Wed, 21 Jun 2017 12:59:06 -0500 - rev 600842
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1357715 - Skip DevTools tests on Stylo that use shadow DOM. r=heycam MozReview-Commit-ID: DXT7yDgPjCM
5d64dcad8becae13b90ae159c6498956f64dcd0b: Bug 1376407 - part2: Emulate selection when committing composition as collapsed to the end of composition r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 27 Jun 2017 03:11:25 -0700 - rev 600841
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1376407 - part2: Emulate selection when committing composition as collapsed to the end of composition r=m_kato When you start new composition during converting with Mozc in e10s mode, the following things occur: 1. Mozc commits previous composition. 2. Gecko dispatches eCompositionCommit event. 3. Mozc sets new composition string (skipping composition start signal). 4. Gecko dispatches eCompositionStart and eCompositionChange event. 5. Selection is changed asynchronously. 6. Gecko sets position of IME windows. At #4, Gecko stores start of composition as selection start, then, trying to adjust it at #5. However, new selection is caret position in new composition string. Therefore, it's not used for the adjustment. This causes that stored composition start offset is always the start of the previous composition (if the previous patch didn't change EnsureToCacheSelection() behavior). So, IMContextWrapper needs to compute proper composition start offset in this case. The simplest fix is, modifying selection at #2 as which will be occurred in focused editor. So, this patch makes the selection cache collapsed to the end of committing string. Note that actual selection may be different if JS changes selection and/or the text in the focused editor. However, it doesn't matter. IMContextWrapper should behave as expected while current composition is active. MozReview-Commit-ID: 221mDUd8yRP
389de2cfc4813637eed01c9e8e5a88e4bb4e5695: Bug 1376407 - part1: IMContextWrapper should cache selected string instead of length of selection r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 27 Jun 2017 02:46:08 -0700 - rev 600840
Push 65884 by bmo:emilio+bugs@crisal.io at Tue, 27 Jun 2017 21:24:14 +0000
Bug 1376407 - part1: IMContextWrapper should cache selected string instead of length of selection r=m_kato IMContextWrapper::EnsureToCacheSelection() always queries actual selection when the caller needs selected string. However, this may be expensive and this is bad behavior for the following patch because it wants to emulate selection range until receiving next selection change notification. Therefore, this patch makes IMContextWrapper::Selection store selected string instead of just its length like other native IME handlers Additionally, this patch renames IMContextWrapper::mSelectedString to IMContextWrapper::mSelectedStringRemovedByComposition for making the difference between it and the new string in Selection clearer. MozReview-Commit-ID: 3bygvW7sKf4
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip