71dcf85b44355ec0be7069df9918c777ea03fa5b: Bug 1275914 part.3 TextComposition should use IMEContentObserver or ContentEventHandler directly when it queries the selection r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 10 Jun 2016 19:45:21 +0900 - rev 379992
Push 21107 by masayuki@d-toybox.com at Mon, 20 Jun 2016 10:09:39 +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
a1831ee8d08078675fd4c5f49419c6ebe69bef11: Bug 1275914 part.2 Modify TextComposition::mCompositionStartOffset after every composition event dispatch r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 10 Jun 2016 19:32:49 +0900 - rev 379991
Push 21107 by masayuki@d-toybox.com at Mon, 20 Jun 2016 10:09:39 +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
e134a9ad6fca415b31c994e0e07b99abdb9d5db1: Bug 1275914 part.1 TextComposition should store target clause offset from start of the composition instead of start of the editor r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 02 Jun 2016 14:26:47 +0900 - rev 379990
Push 21107 by masayuki@d-toybox.com at Mon, 20 Jun 2016 10:09:39 +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
41dd4b3d411bfb6e110ee782cc047b2b6aafd27b: Bug 1280872 - Fix WasmLoop code to use RootedWasmInstanceObject. r=bbouvier draft
Christian Holler <choller@mozilla.com> - Mon, 20 Jun 2016 12:03:39 +0200 - rev 379989
Push 21106 by choller@mozilla.com at Mon, 20 Jun 2016 10:04:47 +0000
Bug 1280872 - Fix WasmLoop code to use RootedWasmInstanceObject. r=bbouvier MozReview-Commit-ID: 1mrfGVSMsuR
e9723c6c6136e2311374e5e6d4ea9cdc9f42b6b3: Bug 1264365 - Disable hardware acceleration for small popup widgets. r=dvander
Nicolas Silva <nsilva@mozilla.com> - Thu, 21 Apr 2016 12:20:31 +0200 - rev 379988
Push 21106 by choller@mozilla.com at Mon, 20 Jun 2016 10:04:47 +0000
Bug 1264365 - Disable hardware acceleration for small popup widgets. r=dvander
4517cfdd7f7997324aacf013102334b4aab1b09a: Bug 1277090: Update tests to get properties instead of attributes r=ato
David Burns <dburns@mozilla.com> - Tue, 31 May 2016 23:52:34 +0100 - rev 379987
Push 21106 by choller@mozilla.com at Mon, 20 Jun 2016 10:04:47 +0000
Bug 1277090: Update tests to get properties instead of attributes r=ato Due to the conflation, we were returning the wrong thing on get_attribute, Updated tests to call get_property when that is what they meant. MozReview-Commit-ID: AY6bd3RECvV
7be72cdc9d7801fced2f4496e1c5b14eb6c0fa9a: Bug 1277090: Have Marionette return only attributes from getElementAttribute. r=ato
David Burns <dburns@mozilla.com> - Tue, 31 May 2016 23:23:05 +0100 - rev 379986
Push 21106 by choller@mozilla.com at Mon, 20 Jun 2016 10:04:47 +0000
Bug 1277090: Have Marionette return only attributes from getElementAttribute. r=ato Using the Selenium atom we are conflating properties and attributes which is not thing we really want to be doing. MozReview-Commit-ID: HdZOz1jQrwz
3c5025f98e561a20e24d97c91a9e4e0ec28015ea: Bug 1280422: Remove unneeded "box-sizing: padding-box" CSS from 3 reftests, now that it's become invalid CSS. (test only, no review.)
Daniel Holbert <dholbert@cs.stanford.edu> - Mon, 20 Jun 2016 09:28:29 +0100 - rev 379985
Push 21106 by choller@mozilla.com at Mon, 20 Jun 2016 10:04:47 +0000
Bug 1280422: Remove unneeded "box-sizing: padding-box" CSS from 3 reftests, now that it's become invalid CSS. (test only, no review.) As it happens, these testcases don't actually have any padding. So for them, "box-sizing: padding-box" is equivalent to the default "content-box" behavior, anyway. So, this change (and the unsupporting of 'padding-box') doesn't impact these tests' rendering. MozReview-Commit-ID: JPTwmahnOti
8f0d4dcde00adf6f6be6e969e7085eb4081a6b4e: Bug 1280280 - Update cubeb to 073c9f011114. r=kinetik
Paul Adenot <paul@paul.cx> - Thu, 16 Jun 2016 14:52:51 +0100 - rev 379984
Push 21106 by choller@mozilla.com at Mon, 20 Jun 2016 10:04:47 +0000
Bug 1280280 - Update cubeb to 073c9f011114. r=kinetik MozReview-Commit-ID: 8mARVNKAG7P
bef268bc063adeae974b588d63b3850747e15a6d: Bug 1280280 - Update `media/libcube/update.sh` to add `cubeb_jack.cpp`, and sort the list of files. r=kinetik
Paul Adenot <paul@paul.cx> - Wed, 15 Jun 2016 17:26:54 +0100 - rev 379983
Push 21106 by choller@mozilla.com at Mon, 20 Jun 2016 10:04:47 +0000
Bug 1280280 - Update `media/libcube/update.sh` to add `cubeb_jack.cpp`, and sort the list of files. r=kinetik MozReview-Commit-ID: 5gwM71sotV2
3ddf6bae09dc3467b7176eaa7be9a52086d05d8e: Bug 1276028 - Baldr: store names as offsets into bytecode (r=bbouvier)
Luke Wagner <luke@mozilla.com> - Sun, 19 Jun 2016 00:29:11 +0100 - rev 379982
Push 21106 by choller@mozilla.com at Mon, 20 Jun 2016 10:04:47 +0000
Bug 1276028 - Baldr: store names as offsets into bytecode (r=bbouvier)
e17bcc6151fecf57e467bd2e9feb9e97401ad459: Bug 1275914 part.8 TextComposition should always update its composition start offset during composing r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 20 Jun 2016 16:34:40 +0900 - rev 379981
Push 21105 by masayuki@d-toybox.com at Mon, 20 Jun 2016 09:32:39 +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
f3d79e816b11a1d227618ac385aa3fbb2f290b41: Bug 1275914 part.7 Add automated tests to query IME selections r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 20 Jun 2016 16:31:29 +0900 - rev 379980
Push 21105 by masayuki@d-toybox.com at Mon, 20 Jun 2016 09:32:39 +0000
Bug 1275914 part.7 Add automated tests to query IME selections r?smaug MozReview-Commit-ID: GwBU6Evcpfa
f5a52b628dbc40ec58c80508f1826767310c8c5c: Bug 1275914 part.6 ContentEventHandler::OnQuerySelectedText() shouldn't refer anchor and focus of selection if there are 2 or more selection ranges r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Sat, 11 Jun 2016 22:22:10 +0900 - rev 379979
Push 21105 by masayuki@d-toybox.com at Mon, 20 Jun 2016 09:32:39 +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
9b6274fb700edaeef664f097ccc985e83121154d: Bug 1275914 part.5 Support special selections at handling eQuerySelectedText r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 20 Jun 2016 16:25:58 +0900 - rev 379978
Push 21105 by masayuki@d-toybox.com at Mon, 20 Jun 2016 09:32:39 +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
8ffd8e57f2230c6ba5a478fa423dc325098984a5: Bug 1280814 - Prevent the media::Interval crash due to the unexpected playback position. r=rillian draft
bechen <bechen@mozilla.com> - Mon, 20 Jun 2016 15:58:58 +0800 - rev 379977
Push 21104 by bechen@mozilla.com at Mon, 20 Jun 2016 08:27:07 +0000
Bug 1280814 - Prevent the media::Interval crash due to the unexpected playback position. r=rillian MozReview-Commit-ID: AZ9Gb2Y0wDF
4e54a6f3ed72d87addf6eb2c3ac76b16366c284b: Bug 1275142 - Don't create animate SVG along with its parent element at the same time. r? draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 16:59:49 +0900 - rev 379976
Push 21103 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 08:01:09 +0000
Bug 1275142 - Don't create animate SVG along with its parent element at the same time. r? If we create an animate SVG along with its parent, in rare cases, the animation does not start in the first frame, i.e, it's the frame that the animated element and its parent element are created. In such cases, restyle for the animation is not observed in the first frame. To avoid it, we need to create parent element in the first place, then, append an animated element into the parent in the next frame. MozReview-Commit-ID: 3GPDxX4cmkQ
145fde077fb42050581115f72a6b6aff1a72f5e9: Bug 1213517 - Wire up getSettings(). draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Mon, 20 Jun 2016 00:38:25 -0400 - rev 379975
Push 21102 by jbruaroey@mozilla.com at Mon, 20 Jun 2016 07:17:37 +0000
Bug 1213517 - Wire up getSettings(). MozReview-Commit-ID: EX5FIo3rCoi
3885236e8ff2aca5d99a7beae8197d0c423b9dd8: Bug 1213517 - Let cam access in competing tabs get closer to their ideals when a tab closes. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Sat, 18 Jun 2016 19:09:39 -0400 - rev 379974
Push 21102 by jbruaroey@mozilla.com at Mon, 20 Jun 2016 07:17:37 +0000
Bug 1213517 - Let cam access in competing tabs get closer to their ideals when a tab closes. MozReview-Commit-ID: htWkYMm18U
ad5d69fefef7ae316f50563274b5afd61dfde4a0: Bug 1213517 - Consolidate camera Allocate's and Restart's constraints logic. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Sat, 18 Jun 2016 16:11:54 -0400 - rev 379973
Push 21102 by jbruaroey@mozilla.com at Mon, 20 Jun 2016 07:17:37 +0000
Bug 1213517 - Consolidate camera Allocate's and Restart's constraints logic. MozReview-Commit-ID: CrARq0QZzrO
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip