1ee5fb218ea1d28e9ea407c897fe091749d72ab9: Bug 1271653 - Debugger::wrapDebuggeeObject should return a DebuggerObject;r=fitzgen
Eddy Bruel <ejpbruel@mozilla.com> - Tue, 21 Jun 2016 11:34:34 +0200 - rev 302156
Push 78625 by ejpbruel@mozilla.com at Tue, 21 Jun 2016 09:34:46 +0000
Bug 1271653 - Debugger::wrapDebuggeeObject should return a DebuggerObject;r=fitzgen
7bf21c554c3d7c854bfa7e38e19b3d7315c99b73: Bug 1271653 - DebuggerObject.getPrototypeOf should return a DebuggerObject;r=fitzgen
Eddy Bruel <ejpbruel@mozilla.com> - Tue, 21 Jun 2016 11:27:37 +0200 - rev 302155
Push 78624 by ejpbruel@mozilla.com at Tue, 21 Jun 2016 09:34:13 +0000
Bug 1271653 - DebuggerObject.getPrototypeOf should return a DebuggerObject;r=fitzgen
0d37cdf53b89ab0a13f6c1df4691e11a9d443d86: Bug 1271653 - DebuggerObject.boundTargetFunction should return a DebuggerObject;r=fitzgen
Eddy Bruel <ejpbruel@mozilla.com> - Tue, 21 Jun 2016 11:20:58 +0200 - rev 302154
Push 78623 by ejpbruel@mozilla.com at Tue, 21 Jun 2016 09:21:50 +0000
Bug 1271653 - DebuggerObject.boundTargetFunction should return a DebuggerObject;r=fitzgen
1c0c5bcadebdd5a65b395637312ac7f4b9935343: Bug 1271653 - DebuggerObject.global should return a DebuggerObject;r=fitzgen
Eddy Bruel <ejpbruel@mozilla.com> - Tue, 21 Jun 2016 11:14:45 +0200 - rev 302153
Push 78622 by ejpbruel@mozilla.com at Tue, 21 Jun 2016 09:15:00 +0000
Bug 1271653 - DebuggerObject.global should return a DebuggerObject;r=fitzgen
333518a265a209bec3a25ef6caeb993292439878: Bug 1280101 - Remove check for window sizes larger than screen; r=automatedtester
Andreas Tolfsen <ato@mozilla.com> - Tue, 14 Jun 2016 18:58:15 +0100 - rev 302152
Push 78621 by atolfsen@mozilla.com at Tue, 21 Jun 2016 08:21:34 +0000
Bug 1280101 - Remove check for window sizes larger than screen; r=automatedtester MozReview-Commit-ID: K2l0pPfGbGp
eca2ce2b6dd2d80969bf0d8e55593db4a37cddc8: Bug 1280101 - Do not coerce window dimensions to integer; r=automatedtester
Andreas Tolfsen <ato@mozilla.com> - Tue, 14 Jun 2016 18:57:02 +0100 - rev 302151
Push 78621 by atolfsen@mozilla.com at Tue, 21 Jun 2016 08:21:34 +0000
Bug 1280101 - Do not coerce window dimensions to integer; r=automatedtester The specification says nothing about coercing to integer. MozReview-Commit-ID: Cq5Wbo2vIAD
fa1be718504b05150a3489bae2ee0035d4f26ecf: Bug 1185307 part.2 Replace upcast from nsISelection to mozilla::dom::Selection with nsISelection::AsSelection() r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 17 Jun 2016 22:32:49 +0900 - rev 302150
Push 78620 by masayuki@d-toybox.com at Tue, 21 Jun 2016 07:57:07 +0000
Bug 1185307 part.2 Replace upcast from nsISelection to mozilla::dom::Selection with nsISelection::AsSelection() r=smaug MozReview-Commit-ID: Gs3oiAgJFG9
fd0960e658109b1e1b613a835279d08a5108d244: Bug 1185307 part.1 Add nsISelection::AsSelection() r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 17 Jun 2016 16:16:10 +0900 - rev 302149
Push 78620 by masayuki@d-toybox.com at Tue, 21 Jun 2016 07:57:07 +0000
Bug 1185307 part.1 Add nsISelection::AsSelection() r=smaug This patch adds nsISelection::AsSelection() for safer "upcast". MozReview-Commit-ID: LlxoMaU0oE
bbe31ff52ae422e4133e0eea6a1dcebba990100e: Bug 1275918 part.2 Update TextComposition::mCompositionStartOffset when it's modified in the remote process r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 14 Jun 2016 21:06:34 +0900 - rev 302148
Push 78619 by masayuki@d-toybox.com at Tue, 21 Jun 2016 07:52:45 +0000
Bug 1275918 part.2 Update TextComposition::mCompositionStartOffset when it's modified in the remote process r=m_kato MozReview-Commit-ID: H1SJTWWav6G
eefc9532e7152d0b03e9489af0b54a1df7ea29f8: Bug 1275918 part.1 ContentCache should retrieve the latest composition start offset from TextComposition and send it to the parent process r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 13 Jun 2016 18:17:58 +0900 - rev 302147
Push 78619 by masayuki@d-toybox.com at Tue, 21 Jun 2016 07:52:45 +0000
Bug 1275918 part.1 ContentCache should retrieve the latest composition start offset from TextComposition and send it to the parent process r=m_kato MozReview-Commit-ID: EoMZtqoMue3
0cefc193909c8878ca39cae149a36f3d08739e82: Bug 1280814 - Prevent the media::Interval crash due to the unexpected playback position. r=rillian
bechen <bechen@mozilla.com> - Mon, 20 Jun 2016 15:58:58 +0800 - rev 302146
Push 78618 by cbook@mozilla.com at Tue, 21 Jun 2016 07:32:37 +0000
Bug 1280814 - Prevent the media::Interval crash due to the unexpected playback position. r=rillian MozReview-Commit-ID: AZ9Gb2Y0wDF
0aeee92e288e305a6c29a683a48a9c7a5fc7c079: Bug 1275914 part.8 TextComposition should always update its composition start offset during composing r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 20 Jun 2016 16:34:40 +0900 - rev 302145
Push 78617 by masayuki@d-toybox.com at Tue, 21 Jun 2016 06:58:42 +0000
Bug 1275914 part.8 TextComposition should always update its composition start offset during composing r=smaug TextComposition should update its composition start offset after every DOM event dispatch with first clause's selection type if there is composition string. MozReview-Commit-ID: HFkePci1PhU
d758ecd88650be969181e8add7423721ea54a7fc: Bug 1275914 part.7 Add automated tests to query IME selections r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 20 Jun 2016 16:31:29 +0900 - rev 302144
Push 78617 by masayuki@d-toybox.com at Tue, 21 Jun 2016 06:58:42 +0000
Bug 1275914 part.7 Add automated tests to query IME selections r=smaug MozReview-Commit-ID: GwBU6Evcpfa
68e44df1e61e9d06ea976c4914709347c4305d41: Bug 1275914 part.6 ContentEventHandler::OnQuerySelectedText() shouldn't refer anchor and focus of selection if there are 2 or more selection ranges r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Sat, 11 Jun 2016 22:22:10 +0900 - rev 302143
Push 78617 by masayuki@d-toybox.com at Tue, 21 Jun 2016 06:58:42 +0000
Bug 1275914 part.6 ContentEventHandler::OnQuerySelectedText() shouldn't refer anchor and focus of selection if there are 2 or more selection ranges r=smaug Selection's focus and anchor node and offset are stored only for the last range. However, ContentEventHandler needs its first range. Therefore, ContentEventHandler shouldn't refer them if there are two or more selection ranges. MozReview-Commit-ID: ACflFE3ZrOM
76c08df53e1a400a102c0296a24c34dad8663197: Bug 1275914 part.5 Support special selections at handling eQuerySelectedText r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 21 Jun 2016 13:13:11 +0900 - rev 302142
Push 78617 by masayuki@d-toybox.com at Tue, 21 Jun 2016 06:58:42 +0000
Bug 1275914 part.5 Support special selections at handling eQuerySelectedText r=smaug TextComposition needs to query first IME selection. Therefore, we need to add support to query special selection range with eQuerySelectedText. First, WidgetQueryContentEvent::mInput should have mSelectionType which should be initialized with InitForQuerySelectedText() but unfortunately, there is no method for eQuerySelectedText. Therefore, this patch initializes WidgetQueryContentEvent::mInit::mSelectionType with SelectionType::eNormal in its constructor. Next, ContentEventHandler needs to support to handle eQuerySelectedText with special selection types. However, we need to create 2 paths in some cases, one is for normal selection and the other is for special selections because there are no selection ranges may be usual case for special selections but not so for normal selection. Therefore, ContentEventHandler::InitCommon() becomes a little bit more complicated. ContentEventHandler::mSelection and ContentEventHandler::mFirstSelectedRange is initialized with the specified selection type but normal selection type is also necessary to compute the selection root since the selection root is computed from the first selected range which may not be anywhere if its selection type is not normal. Finally, ContentEventHandler::OnQuerySelectedText() returns "there are no selections" as succeeded case in special selection type cases. MozReview-Commit-ID: 9WzUx8b5piw
c3d1a45c8796948e95d3e93bc3d98f0583d97a11: Bug 1275914 part.4 Add a method to retrieve focused content's selection controller to nsIPresShell r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 10 Jun 2016 21:01:32 +0900 - rev 302141
Push 78617 by masayuki@d-toybox.com at Tue, 21 Jun 2016 06:58:42 +0000
Bug 1275914 part.4 Add a method to retrieve focused content's selection controller to nsIPresShell r=smaug ContentEventHandler will need to support query any types of selection. Therefore, it cannot use nsCopySupport::GetSelectionForCopy(). Instead, a part of it should be implemented by nsIPresShell::GetSelectionControllerForFocusedContent() and it should be shared by nsCopySupport::GetSelectionForCopy() and ContentEventHandler. MozReview-Commit-ID: 1ItkkIUPFMG
dd927e5e00a29d9998029e8f80dad8582e0d0fba: Bug 1275914 part.3 TextComposition should use IMEContentObserver or ContentEventHandler directly when it queries the selection r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 10 Jun 2016 19:45:21 +0900 - rev 302140
Push 78617 by masayuki@d-toybox.com at Tue, 21 Jun 2016 06:58:42 +0000
Bug 1275914 part.3 TextComposition should use IMEContentObserver or ContentEventHandler directly when it queries the selection r=smaug TextComposition queries selection start offset a lot of times. Therefore, for reducing the runtime cost, it should use IMEContentObserver if it's available or ContentEventHandler, otherwise. MozReview-Commit-ID: 61GgQZDX2HP
a6edf7da37d329841a3cf637678a26a6a5090506: Bug 1275914 part.2 Modify TextComposition::mCompositionStartOffset after every composition event dispatch r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 10 Jun 2016 19:32:49 +0900 - rev 302139
Push 78617 by masayuki@d-toybox.com at Tue, 21 Jun 2016 06:58:42 +0000
Bug 1275914 part.2 Modify TextComposition::mCompositionStartOffset after every composition event dispatch r=smaug When composition string hasn't been non-empty, insertion point of the composition string can be changed by a DOM event handler. E.g., compositionstart, first compositionupdate and first text. Therefore, TextComposition should update the composition start offset cache after every event dispatch. MozReview-Commit-ID: FOPewPTRuCn
b202c72df4f1165926de1d00772b78f97ac66e4d: Bug 1275914 part.1 TextComposition should store target clause offset from start of the composition instead of start of the editor r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 02 Jun 2016 14:26:47 +0900 - rev 302138
Push 78617 by masayuki@d-toybox.com at Tue, 21 Jun 2016 06:58:42 +0000
Bug 1275914 part.1 TextComposition should store target clause offset from start of the composition instead of start of the editor r=smaug It's enough to store target clause offset from start of the composition and better to modify mCompositionStartOffset because when even if mCompositionStartOffset is changed, we don't need to modify the target clause offset. This patch renames mCompositionTargetOffset to mTargetClauseOffsetInComposition. MozReview-Commit-ID: 1wt2OTUUjkY
e15474388a5ff4a49fcea922a2e74ae2a0aff0d7: Bug 1280252 - Refactor RareArgumentsData a bit so it behaves correctly on moving GC. r=luke
Jan de Mooij <jdemooij@mozilla.com> - Tue, 21 Jun 2016 08:49:09 +0200 - rev 302137
Push 78616 by jandemooij@gmail.com at Tue, 21 Jun 2016 06:50:07 +0000
Bug 1280252 - Refactor RareArgumentsData a bit so it behaves correctly on moving GC. r=luke
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip