cd0f006ea4b311f6223c6d151f09aa9758c7ad92: Bug 1447239 - Implement InputEvent.inputType r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 07 Jan 2019 10:10:57 +0000 - rev 452704
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1447239 - Implement InputEvent.inputType r=smaug This patch implements InputType.inputType which is declared by Input Events. The attribute has already been implemented by Chrome and Safari. Chrome implements Input Events Level 1, but Safari implements Input Events Level 2. Difference between them is only whether it supports "insertFromComposition", "deleteByComposition" and "deleteCompositionText". This patch makes the level switchable with pref and takes Level 1 by default because Level 2 is still unstable around event order with composition events. For reducing string copy cost at dispatching "input" event, this patch makes EditorInternalInputEvent store valid input-type as enum class, EditorInputType and resolves it to string value when dom::InputEvent::GetInputType() is called. Note that the reason why this patch names the enum class as EditorInputType is, there is InputType enum class already for avoiding conflict the name, this appends "Editor" prefix because "input" and "beforeinput" events are fired only when an editor has focus. Differential Revision: https://phabricator.services.mozilla.com/D14128
f8237a1e70b899fb91131718054f2d9e53bc082c: Bug 1447239 - Make WPT for InputEvent.inputType of each execCommand should test each call separately r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 07 Jan 2019 10:09:51 +0000 - rev 452703
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1447239 - Make WPT for InputEvent.inputType of each execCommand should test each call separately r=smaug The WPT for InputEvent.inputType of each execCommand runs all tests in a test function. Therefore, even if there is an unexpected result, it won't test other part. Additionally, it tests execCommand's result of the DOM tree in the contenteditable so that it's not useful for checking InputEvent.inputType for now. Therefore, this patch makes the test returns error for each result of each call of execCommand. Additionally, it sets contenteditable attribute to a <p> element which cannot store other block elements like <ul>, <ol>, <div>, etc. Therefore, some of the execCommand won't work on Gecko since Gecko's editor does not create invalid child elements as far as possible. Therefore, this patch makes it a <div> element. And also adding "insertHorizontalRule", "backColor", "foreColor", "hilightColor", "fontName", "createLink", "unlink". inputType values for those commands are defined by current spec. So, if they'd be changed, we could detect it quickly. Differential Revision: https://phabricator.services.mozilla.com/D14123
658f77e5e78bf4efa3dce011f4aae33139206f7e: No Bug, taskcluster/docker/funsize-update-generator pipfile-update. r=sfraser
ffxbld <ffxbld@mozilla.com> - Mon, 07 Jan 2019 11:14:06 +0000 - rev 452702
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
No Bug, taskcluster/docker/funsize-update-generator pipfile-update. r=sfraser Differential Revision: https://phabricator.services.mozilla.com/D15807
624782f944fc58580c3f1beeb59f9ef0c6a6f127: Bug 1517511 - Simplify computed::LengthOrPercentage and friends. r=heycam
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 07 Jan 2019 11:00:27 +0000 - rev 452701
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1517511 - Simplify computed::LengthOrPercentage and friends. r=heycam This is a first step to share LengthOrPercentage representation between Rust and Gecko. We need to preserve whether the value came from a calc() expression, for now at least, since we do different things depending on whether we're calc or not right now. See https://github.com/w3c/csswg-drafts/issues/3482 and dependent bugs for example. That means that the gecko conversion code needs to handle calc() in a bit of an awkward way until I change it to not be needed (patches for that incoming in the next few weeks I hope). I need to add a hack to exclude other things from the PartialEq implementation because the new conversion code is less lossy than the old one, and we relied on the lousiness in AnimationValue comparison (in order to start transitions and such, in [1] for example). I expect to remove that manual PartialEq implementation as soon as I'm done with the conversion. The less lossy conversion does fix a few serialization bugs for animation values though, like not loosing 0% values in calc() when interpolating lengths and percentages, see the two modified tests: * property-types.js * test_animation_properties.html Differential Revision: https://phabricator.services.mozilla.com/D15793
76c4b7d2ae72a58f13fc2806826be655c27c5c93: Bug 1518024 - Go back to setting style.direction on the awesomebar popup because automplete.xml expects this. r=mak
Dão Gottwald <dao@mozilla.com> - Mon, 07 Jan 2019 10:45:20 +0000 - rev 452700
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1518024 - Go back to setting style.direction on the awesomebar popup because automplete.xml expects this. r=mak Differential Revision: https://phabricator.services.mozilla.com/D15803
ac819553ec263f7d13e67ac720bde50bdbca6887: Bug 1508435 - Enable browser_markup_screenshot_node_shadowdom;r=jmaher
Julian Descottes <jdescottes@mozilla.com> - Mon, 07 Jan 2019 09:56:14 +0000 - rev 452699
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1508435 - Enable browser_markup_screenshot_node_shadowdom;r=jmaher I just landed the patch that fixes this intermittent, can we reenable? Differential Revision: https://phabricator.services.mozilla.com/D15806
df193b44f65ab8fe8b249d1690b95c752bf93bde: Mergemozilla-central to autoland. a=merge CLOSED TREE
Oana Pop Rus <opoprus@mozilla.com> - Mon, 07 Jan 2019 11:59:43 +0200 - rev 452698
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Mergemozilla-central to autoland. a=merge CLOSED TREE
ed6cbd03dbc20866e472a587cf3275d78b01adcc: Bug 1508435 - Wait for one second between each screenshot test;r=pbro
Julian Descottes <jdescottes@mozilla.com> - Mon, 07 Jan 2019 09:23:21 +0000 - rev 452697
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1508435 - Wait for one second between each screenshot test;r=pbro Differential Revision: https://phabricator.services.mozilla.com/D15512
fc3e620149eced94848e3a548616addb0fd6833e: Bug 1517710 - Avoid calling SetPullingEnabled on a destroyed MediaStream. r=padenot
Andreas Pehrson <apehrson@mozilla.com> - Mon, 07 Jan 2019 08:24:08 +0000 - rev 452696
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1517710 - Avoid calling SetPullingEnabled on a destroyed MediaStream. r=padenot Differential Revision: https://phabricator.services.mozilla.com/D15798
65266c77b815e0ee6e8472525df7ba24c2726c73: Bug 1518044 - Pass FULL_PAINT_TIME value to CONTENT_FRAME_TIME calculation for non-WR. r=jrmuizel
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 07 Jan 2019 03:18:52 +0000 - rev 452695
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1518044 - Pass FULL_PAINT_TIME value to CONTENT_FRAME_TIME calculation for non-WR. r=jrmuizel This will let us get the MissedCompositeLow/Mid/Long variants in the CFT_REASON telemetry output. Differential Revision: https://phabricator.services.mozilla.com/D15797
89f55d26acaf0c33144c577029b7b58d490bec62: Bug 1518044 - Record SVG and UPLOAD specific variants of CONTENT_FRAME_TIME using the vsync based timings. r=jrmuizel
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 07 Jan 2019 03:17:42 +0000 - rev 452694
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1518044 - Record SVG and UPLOAD specific variants of CONTENT_FRAME_TIME using the vsync based timings. r=jrmuizel We're switching to prefering the vsync version, so making these diagnostic equivalents use that timing should be more useful. I think leaving the profiler marker (which uses ms, not vsync%) showing just the graphics component still makes sense. Differential Revision: https://phabricator.services.mozilla.com/D15796
dad482c7ff924d880604b1eba8f73437a823c069: Bug 1518044 - Use shared CONTENT_FRAME_TIME calculation for non-WebRender. r=jrmuizel
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 07 Jan 2019 03:15:57 +0000 - rev 452693
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1518044 - Use shared CONTENT_FRAME_TIME calculation for non-WebRender. r=jrmuizel This also results in us getting the CONTENT_FRAME_TIME profiler markers added for non-WR. Differential Revision: https://phabricator.services.mozilla.com/D15795
39ab423f06ef236d72d25629bb462200ed8483ef: Bug 1518044 - Move CONTENT_FRAME_TIME calculation code into CompositorBridgeParent. r=jrmuizel
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 07 Jan 2019 03:14:28 +0000 - rev 452692
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1518044 - Move CONTENT_FRAME_TIME calculation code into CompositorBridgeParent. r=jrmuizel This shouldn't change any behaviour, just puts the code into a separate function so that it's easier to follow. Differential Revision: https://phabricator.services.mozilla.com/D15794
1541218476834334f1e5af8b22671ff75b4c54b0: Bug 1325850 - part 2: Add automated tests for nsIContentIterator concrete classes r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 03 Jan 2019 22:27:47 +0000 - rev 452691
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1325850 - part 2: Add automated tests for nsIContentIterator concrete classes r=smaug nsContentIterator in post-order collects nodes starting from deepest first child to next siblings and parents. I.e., collecting end points (i.e., "close tag" if element node). This is tested by test_content_iterator_post_order.html. nsContentIterator in pre-order collects nodes starting from most ancestor to last deepest child node. I.e., collecting start points (i.e., "open tag" if element node). This is tested by test_content_iterator_pre_order.html. nsContentSubtreeIterator collects most ancestor nodes which are selected entirely by specified range or positions. This is tested by test_content_iterator_subtree.html I.e., all of them start with "test_content_iterator_" for making find easier. Differential Revision: https://phabricator.services.mozilla.com/D15286
7cf2438bcd343bcd530e8e9f8e8e9c4cc92942e4: Bug 1325850 - part 1: Create ScriptableContentIterator to make each concrete class of nsIContentIterator scriptable r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 03 Jan 2019 22:19:04 +0000 - rev 452690
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1325850 - part 1: Create ScriptableContentIterator to make each concrete class of nsIContentIterator scriptable r=smaug The concrete classes of nsIContentIterator are enough complicated, but they are not tested simply. Therefore, it's dangerous to touch them even if we meed bugs of them. Additionally, it's used in some hot paths, therefore, I'd like to keep them simple as far as possible. Therefore, this patch creates a mediator class between script and each nsIContentIterator instance. So, this change shouldn't affect any of actual behavior nor performance. Differential Revision: https://phabricator.services.mozilla.com/D15285
eb6cf8333a9aac70bddfa87b670dbce922fbe058: Bug 1517175 - Part 2: Add about:memory filter r=njn
Cameron McCormack <cam@mcc.id.au> - Mon, 07 Jan 2019 03:04:46 +0000 - rev 452689
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1517175 - Part 2: Add about:memory filter r=njn Depends on D15628 Differential Revision: https://phabricator.services.mozilla.com/D15629
79dfd716ddeb583bf14d27281e4531d976db3d3f: Bug 1517175 - Part 1: Omit "Other Measurements" section when empty r=njn
Cameron McCormack <cam@mcc.id.au> - Mon, 07 Jan 2019 03:04:44 +0000 - rev 452688
Push 110957 by cbrindusan@mozilla.com at Mon, 07 Jan 2019 16:50:15 +0000
Bug 1517175 - Part 1: Omit "Other Measurements" section when empty r=njn Differential Revision: https://phabricator.services.mozilla.com/D15628
072522b854f3b8e802e88606b9b5b73cc0884279: Bug 1514112 - listen for font setting changes even if DWrite is not used. r=jrmuizel
Lee Salzman <lsalzman@mozilla.com> - Mon, 07 Jan 2019 11:46:04 -0500 - rev 452687
Push 110956 by lsalzman@mozilla.com at Mon, 07 Jan 2019 16:46:37 +0000
Bug 1514112 - listen for font setting changes even if DWrite is not used. r=jrmuizel
e01254abd76e30e9c55f12b15415b5b20c129bba: Backed out changeset 462d05bad533 (bug 1517653) for assertion failures in z:/build/build/src/js/src\vm/HelperThreads.h:361 CLOSED TREE
shindli <shindli@mozilla.com> - Mon, 07 Jan 2019 18:18:16 +0200 - rev 452686
Push 110955 by shindli@mozilla.com at Mon, 07 Jan 2019 16:19:58 +0000
Backed out changeset 462d05bad533 (bug 1517653) for assertion failures in z:/build/build/src/js/src\vm/HelperThreads.h:361 CLOSED TREE
501ffb16f40b1912877c2448117fdefd76e0b836: Bug 1517158 - add hasGlobal for AbstractFramePtr, DebugFrame and JSScript. r=jonco
Yoshi Cheng-Hao Huang <allstars.chh@gmail.com> - Thu, 03 Jan 2019 13:19:30 +0100 - rev 452685
Push 110954 by allstars.chh@gmail.com at Mon, 07 Jan 2019 15:37:43 +0000
Bug 1517158 - add hasGlobal for AbstractFramePtr, DebugFrame and JSScript. r=jonco To prevent triggering read barrier while accessing GlobalObject.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip