62a06e867ea05fb802a5ec7acf4b96fa3d23c659: Bug 1377752 - part1: Add automated test for checking scroll position and focused document when setting selection into a contenteditable element in an iframe element r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 05 Jul 2017 22:21:43 +0900 - rev 604232
Push 67016 by masayuki@d-toybox.com at Wed, 05 Jul 2017 16:47:06 +0000
Bug 1377752 - part1: Add automated test for checking scroll position and focused document when setting selection into a contenteditable element in an iframe element r?smaug When an iframe doesn't have focus, moving selection into a contenteditable element in it shouldn't cause moving focus to the document, moving focus to the editable element nor scrolling to the editor but the editor should become active element. When an iframe has focus, moving selection into a contenteditable element in it should cause moving focus to the editor and scroll it into the view. MozReview-Commit-ID: 1ZDPj6UotLn
4cb35674240c623f8a0b1efc38cbc42cd6a55539: Bug 1377672 - part5: IMEStateManager::OnChangeFocusInternal() should notify IME of blur when focus is moving from a remote process to another process r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 05 Jul 2017 16:26:41 +0900 - rev 604231
Push 67016 by masayuki@d-toybox.com at Wed, 05 Jul 2017 16:47:06 +0000
Bug 1377672 - part5: IMEStateManager::OnChangeFocusInternal() should notify IME of blur when focus is moving from a remote process to another process r?m_kato When focus is moving from a remote process to different process (including to the main process), destroying IMEContentObserver in the focused remote process occurs later. I.e., NOTIFY_IME_OF_BLUR will be notified later. However, it may be too late for new focused process especially when destroying the focused widget. Therefore, this patch makes IMEStateManager notifies IME of blur in such case. MozReview-Commit-ID: GkypubVjn3H
151946e931750594c97ca5e7fb70c6f67adb1d53: Bug 1377672 - part4: ContentCacheInParent::RequestIMEToCommitComposition() should ignore too late requests r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 05 Jul 2017 19:55:18 +0900 - rev 604230
Push 67016 by masayuki@d-toybox.com at Wed, 05 Jul 2017 16:47:06 +0000
Bug 1377672 - part4: ContentCacheInParent::RequestIMEToCommitComposition() should ignore too late requests r?m_kato Requests to commit/cancel composition came from remote process with sync message. So, it may be too late. E.g., * If the process already sent new composition start but is not handled by the remote process yet. * If the process already send commit message but it's not handled by the remote process yet. * If focus was already moved to different process. In the former 2 cases, the remote process should wait eCompositionCommit(AsIs) events for clearing TextComposition. Therefore, the requested should be treated as it's handled asynchronously. In the last case, the remote process should commit composition with latest composition string in the main process because if the remote process commits composition with "current" composition string in it, user may lost some inputted text. MozReview-Commit-ID: 18BUoZZq7HS
968b38ca5346c25b344728803c5774026423a571: Bug 1377672 - part3: IMEStateManager::NotifyIME() should ignore notifications and requests which comes from unexpected process r?smaug, m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 06 Jul 2017 00:47:40 +0900 - rev 604229
Push 67016 by masayuki@d-toybox.com at Wed, 05 Jul 2017 16:47:06 +0000
Bug 1377672 - part3: IMEStateManager::NotifyIME() should ignore notifications and requests which comes from unexpected process r?smaug, m_kato IME should receive notifications and requests only from proper process. E.g., IME shouldn't commit composition by a request which came from previous focused process. This patch makes that IMEStateManager::NotifyIME() takes pointer to TabParent optionally. If the request or notification came from remote process, it should be non-nullptr. Then, this makes it ignore notifications and requests from unexpected process. Note that this patch also touches some gfx headers because they use |ipc::| but compiler is confused at the ambiguousness between |mozilla::ipc::| and |mozilla::dom::ipc::|. Finally, this patch changes the NS_ASSERTION in IMEHandler::OnDestroyWindow() to MOZ_ASSERT because the orange caused by the NS_ASSERTION was not realized since there was already an intermittent orange bug caused by different NS_ASSERTION. MozReview-Commit-ID: 9CgKXQRJWmN
4a78b938bb966c8e1aad2f0de099e1235397068a: Bug 1374589 - Port windows tests which require signed builds to in-tree tasks r=Callek draft
Johan Lorenzo <jlorenzo@mozilla.com> - Thu, 29 Jun 2017 13:50:13 -0700 - rev 604228
Push 67015 by bmo:jlorenzo@mozilla.com at Wed, 05 Jul 2017 16:14:41 +0000
Bug 1374589 - Port windows tests which require signed builds to in-tree tasks r=Callek MozReview-Commit-ID: JI0T2qW6P00
599518538471fe07265fd2dd090a4306dcb100e2: Bug 1364876 - Move heapsnapshot native components to /devtools/platform/heapsnapshot. r=fitzgen draft
Alexandre Poirot <poirot.alex@gmail.com> - Thu, 11 May 2017 10:38:04 +0200 - rev 604227
Push 67014 by bmo:poirot.alex@gmail.com at Wed, 05 Jul 2017 16:09:49 +0000
Bug 1364876 - Move heapsnapshot native components to /devtools/platform/heapsnapshot. r=fitzgen MozReview-Commit-ID: Ljm33fuvE2T
4454e87d089c4acf6570461d9cfb358219981cbd: Bug 1378203 - Use canPresent in tabbrowser.xml to determine if we can blank out a tab before switching to it. r?billm draft
Mike Conley <mconley@mozilla.com> - Tue, 04 Jul 2017 22:26:16 -0400 - rev 604226
Push 67013 by mconley@mozilla.com at Wed, 05 Jul 2017 15:56:26 +0000
Bug 1378203 - Use canPresent in tabbrowser.xml to determine if we can blank out a tab before switching to it. r?billm MozReview-Commit-ID: CJEIJYlRHam
4601c2ba6f848ceeeac5db26cfe6621bf7e15a6e: Bug 1377793 - Fix scrolling in the non-Photon main menu. r=Gijs draft
Paolo Amadini <paolo.mozmail@amadzone.org> - Wed, 05 Jul 2017 16:28:58 +0100 - rev 604225
Push 67012 by paolo.mozmail@amadzone.org at Wed, 05 Jul 2017 15:50:50 +0000
Bug 1377793 - Fix scrolling in the non-Photon main menu. r=Gijs MozReview-Commit-ID: 88IsXDvYjyK
87e422a20250f76c62881a9f5eba04ad561bd461: Bug 1378203 - Use canPresent in tabbrowser.xml to determine if we can blank out a tab before switching to it. r?billm draft
Mike Conley <mconley@mozilla.com> - Tue, 04 Jul 2017 22:26:16 -0400 - rev 604224
Push 67011 by mconley@mozilla.com at Wed, 05 Jul 2017 15:50:24 +0000
Bug 1378203 - Use canPresent in tabbrowser.xml to determine if we can blank out a tab before switching to it. r?billm MozReview-Commit-ID: CJEIJYlRHam
18d98935c3c2e0977596492f6fa2098004a10a6f: Bug 1378203 - Add nsITabParent.canPresent. r?billm draft
Mike Conley <mconley@mozilla.com> - Tue, 04 Jul 2017 21:24:42 -0400 - rev 604223
Push 67011 by mconley@mozilla.com at Wed, 05 Jul 2017 15:50:24 +0000
Bug 1378203 - Add nsITabParent.canPresent. r?billm nsITabParent.canPresent is set to true once the child has informed the parent that it has initialized and has enough information to paint something. MozReview-Commit-ID: GgReQT4MTtT
f0db7086321859725e53135d031418d5afc61fc5: Bug 1376484 - Remove ellipsis from Send to Device... page action menu r?eoger draft
Jeongkyu Kim <jeongkyu.kim@gmail.com> - Thu, 06 Jul 2017 00:49:30 +0900 - rev 604222
Push 67010 by bmo:jeongkyu.kim@gmail.com at Wed, 05 Jul 2017 15:50:03 +0000
Bug 1376484 - Remove ellipsis from Send to Device... page action menu r?eoger MozReview-Commit-ID: 6CFdAyRVQIM
50dc29151461cd9c8239ca7f6e47024c34c4d10b: Bug 1378355 - Update GetMaxDisplayPortSize to respect the gfx.max-texture-size pref. r?tnikkel draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 05 Jul 2017 10:29:30 -0400 - rev 604221
Push 67009 by kgupta@mozilla.com at Wed, 05 Jul 2017 15:46:28 +0000
Bug 1378355 - Update GetMaxDisplayPortSize to respect the gfx.max-texture-size pref. r?tnikkel MozReview-Commit-ID: D6wF4QrnGSw
8f2f16fb3144b45c9fbe824097d8a675ef70cf1a: Bug 1378355 - Extract gfxPlatform wrappers for MaxAllocSize and MaxTextureSize. r?Bas draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 05 Jul 2017 10:29:30 -0400 - rev 604220
Push 67009 by kgupta@mozilla.com at Wed, 05 Jul 2017 15:46:28 +0000
Bug 1378355 - Extract gfxPlatform wrappers for MaxAllocSize and MaxTextureSize. r?Bas This allows us to reuse the minimum bound guards on the pref values in other places that want to use the prefs. MozReview-Commit-ID: 7XKuM5u1GB8
e4e414a8d89cc3d5dedcdfddb3d9ad3afb3f9745: Bug 1378355 - Remove unused function. r?Bas draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 05 Jul 2017 10:29:30 -0400 - rev 604219
Push 67009 by kgupta@mozilla.com at Wed, 05 Jul 2017 15:46:28 +0000
Bug 1378355 - Remove unused function. r?Bas MozReview-Commit-ID: H051LFrFMgD
e2ce670781e0890bc06f9d6938c73b7adacef395: Bug 1365133 - Update tests - Part 2. draft
Evan Tseng <evan@tseng.io> - Tue, 20 Jun 2017 15:11:46 +0800 - rev 604218
Push 67008 by bmo:evan@tseng.io at Wed, 05 Jul 2017 15:44:47 +0000
Bug 1365133 - Update tests - Part 2. MozReview-Commit-ID: GoOXdJ4RfY9
5eb95d24adfe89858f6e3e42a8ec42916c8b4473: Bug 1378139 - Add stylo-only talos test suite for perf-reftest singletons; r?igoldan draft
Rob Wood <rwood@mozilla.com> - Wed, 05 Jul 2017 11:17:31 -0400 - rev 604217
Push 67007 by rwood@mozilla.com at Wed, 05 Jul 2017 15:31:19 +0000
Bug 1378139 - Add stylo-only talos test suite for perf-reftest singletons; r?igoldan MozReview-Commit-ID: 77KLUK1VysX
e08b2b19cda7e46ed448c1fd9bb84b26753824e5: Bug 1341304 - Implement devtools.panels.elements.onSelectionChanged. draft
Luca Greco <lgreco@mozilla.com> - Thu, 01 Jun 2017 20:06:53 +0200 - rev 604216
Push 67006 by luca.greco@alcacoop.it at Wed, 05 Jul 2017 15:30:21 +0000
Bug 1341304 - Implement devtools.panels.elements.onSelectionChanged. MozReview-Commit-ID: HMKvnk3wDyX
a8ad21bed7953b59669d5ae7016dd2e75b7690ef: Bug 1377169 - Turn gfxRect into a typedef. r?jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 05 Jul 2017 11:22:00 -0400 - rev 604215
Push 67005 by kgupta@mozilla.com at Wed, 05 Jul 2017 15:22:23 +0000
Bug 1377169 - Turn gfxRect into a typedef. r?jrmuizel One thing to note here is that the Scale function on gfxRect has a different implementation than that in gfx::Rect which is replacing it. The former just scales the width/height directly whereas the latter scales the XMost/YMost and recomputes the width/height. MozReview-Commit-ID: 5FImdIaNfC3
a5cf3a39220f630b7aa545d6482861c65fb05471: Bug 1377169 - Copy some useful functions from gfxRect into other places. r?jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 05 Jul 2017 11:21:58 -0400 - rev 604214
Push 67005 by kgupta@mozilla.com at Wed, 05 Jul 2017 15:22:23 +0000
Bug 1377169 - Copy some useful functions from gfxRect into other places. r?jrmuizel These functions need to survive the gfxRect purge as they are used in a few places. MozReview-Commit-ID: 1jGNlmAvV49
eb506a6ac350ebba23a207c5d2cae1d45e763fb7: Bug 1355924 - Fix assertion related to aContainingBlockISize >=0 and return early from idleCallback if CombinedStopReload was uninitialized before it was called. r?dao draft
Jared Wein <jwein@mozilla.com> - Wed, 05 Jul 2017 11:00:45 -0400 - rev 604213
Push 67004 by bmo:jaws@mozilla.com at Wed, 05 Jul 2017 15:22:20 +0000
Bug 1355924 - Fix assertion related to aContainingBlockISize >=0 and return early from idleCallback if CombinedStopReload was uninitialized before it was called. r?dao This changeset will be folded with the other one before landing. I kept it separate to make reviewing easier. MozReview-Commit-ID: KRDek3Yj520
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip