Previously, every test and support file would be synced to the objdir
when running any test. Now that only those support files and tests requested
are synced, we note support files required beyond those in a test's
directory in ini manifests.
MozReview-Commit-ID: EmlDz9d4lqt
Only text styles should be copied between the replaced element and the input.
Other styles are still copied between the input and the measurement element.
MozReview-Commit-ID: 7YSWtjLgH2z
--HG--
extra : rebase_source : 568ac2a70b6b70e3df97bcb9ab2e55cc693a51b6
Check the "isFrameSwitching" property of the tabNavigated event before
updating the devtools title. If frameSwitching is true, the event is a
fake event generated by the webbrowser actor when switching the frame
context in the devtools.
Added another mochitest to verify this.
MozReview-Commit-ID: LDycPcf0tLv
--HG--
extra : rebase_source : 5b8070a72d081490c5c3c366ee71753d99707dfa
All the other methods use the style
{
myMethod() { ... }
}
while these two methods use
{
myMethod: function () { ... }
}
For consistency, we should use the common style here.
MozReview-Commit-ID: 5rg8uPoULyN
The test used to time out, mainly because we were checking 'Browser styles' on the
computed properties panel, which is quite slow. As the 'Browser styles' checkbox
is already tested in its own test, we can remove it from here, and adapt this test
to take this into account.
MozReview-Commit-ID: CR94qfg73DR
--HG--
extra : transplant_source : I/%A6ZG%D6%C1%12%19%A18%5E%09%83%7D%8B%BA5%C4Q
Should have been a catch.
--HG--
extra : rebase_source : 936da669f5947820788bfa3b7431a866dc38a523
extra : amend_source : 6a11eb98ec399f925fa0c4c15955d08f235f1b1a
When opening the context menu (and displaying the "copy" menu entry)
or when receiving a copy event, we now check if the current target
is a textarea. (multiline inplace editor relies on textarea)
Modified existing test to check this new use case.
MozReview-Commit-ID: Cgm67JCdN4c
--HG--
extra : rebase_source : 4955f910e5428b92587b408ffd1b62cd668faf2a
The default inplace-editor autocomplete behavior is not userfriendly
when combined with a multiline inplace-editor. Navigating up/down might
trigger an autocomplete suggestion.
Also, the autocomplete popup is not displayed at the correct position and
should take the multiline into account.
MozReview-Commit-ID: JTiCQ3HK5bn
--HG--
extra : rebase_source : 001becbe7cfde064b2163e7c2ebcc4aa82e22610
The inplaceEditor now supports a maxWidth configuration option which can either
be a number or a method returning a number. This maxWidth will be applied to the
hidden element used in order to autosize the input.
MozReview-Commit-ID: JTiCQ3HK5bn
--HG--
extra : rebase_source : dcf7ba4a897cd77b43b333ec3b5633dc9043e51d
extra : source : a93558488cf7fc9f54165bd5f98055e8a3901dac
In preparation for using a multiline editor for property values, tests
need to be updated :
- some tests used the "input" selector, which will no longer work with a
textarea
- some tests are relying on EventUtils.sendChar to send keys such as
"VK_RETURN". Doing so also applies the shift key modifier, which has
a specific behavior with multiline editors
MozReview-Commit-ID: HkFxH3Go49E
--HG--
extra : rebase_source : 58ea640905b4acc2574c47b2bc87fcf0780db59b
Error was raised in drawGraphElementBackground when called with the graphView
being `0` This could happen because in animation-timeline.js , there is a
resize event handler that could be fired while the animation panel width is 0.
We fix this by making sure the animation panel does not have a width of zero
in the resize handler.
MozReview-Commit-ID: 71izZnZBX7V
--HG--
extra : transplant_source : Tqx%8A%60Ryi%B6%CE%DDQ%C0%2C%0Br-%F3%08%E6
Add an 'unit-change' event fired when shift+click on color and angle swatches.
Add a listener on this event in text-property-editor.js to call the same function
that's called when tooltip edit is commited to persist the new unit.
Edit some tests to adapt to this new behaviour and create some tests to make sure
the value obtained via shift+click are actually persisted.
MozReview-Commit-ID: CcF4oiBPEzT
--HG--
extra : transplant_source : %1B%40%A24%EDW.%C5%96%C8m%3C%1F4%DA%F78%D1%26%8B
The problem with this test is that loadPageAndGetHud() resolves once the console
message about the request is rendered. However, the message is logged immediately
when enough info has been received instead of waiting for all updates, such as
headers, body and timings, to be received.
By the time the test calls waitForFinishedRequest(PAGE_REQUEST_PREDICATE), the
initial request is still pending and the resulting promise resolves once
the initial GET request finishes instead of the POST request triggered by
the form submission causing the test failures.
MozReview-Commit-ID: HkDdKTmzJfM
--HG--
extra : rebase_source : 3f0af6dd9e359fd440deb0c929ed6d8e04b05638
This commit adds the `getCensusIndividuals` utility for getting the individual
node IDs that match the census leaves specified by the given indices in a
pre-order depth-first traversal of a census report generated with the given
breakdown.
MozReview-Commit-ID: A4IRcP82iCC
--HG--
extra : histedit_source : e48cc59b522ce82f649f077b4686cea4715980f1
The `flatten` function takes an array of arrays and flattens them to a single
array, removing one level of nesting. It does not recursively flatten multiple
levels of nesting.
MozReview-Commit-ID: ErDMHbT2IX
--HG--
extra : histedit_source : eb6e4f8c54f536c84b08da22ef60cfa56a5075c8
The devtools host window updates its title when its target navigates.
This was done using a contentDocument CPOW, and thus failing on e10s.
The url and title are now stored in TabTarget and updated on tab navigation.
Updated existing test to cover the case of pages with a title.
MozReview-Commit-ID: 4G1keOA7yB6
--HG--
extra : rebase_source : 720084e9929f334092ffe18e4c786cbf731fe52e
This commit gives every `CensusTreeNode` instance a `reportLeafIndex` member
that is an index into a pre-order traversal of the census report from which it
was generated. This can be used to get the leaf in the census report
corresponding to a given `CensusTreeNode` instance.
Based on the original patch from danemacmillan.
* suggestion-picker.js
Add a new shared util to find the most popular css property in an array.
The list of popular css properties is extracted from chrome devtools code.
* autocomplete-popup.js
Can specify selected item index when opening the popup or setting items.
* inplace-editor.js
Use the suggestion-picker to select a default property.
MozReview-Commit-ID: JuWZzbBSBqX
--HG--
extra : rebase_source : 3317766ae63aea83f845d3cf3d134ecf60135f67
Changes the way that source files are loaded in the editor. Previously,
source text and mode were set on the existing editor document.
Now, source files are their own CodeMirror Documents, so when it comes time
to showing them in the editor, it's just a matter of swapping one
document for another.
Notes:
+ The DebuggerView now has a _setEditorDocument method for showing a
source document
+ The Editor now has support for creating documents and replacing
documents.
MozReview-Commit-ID: HrkiHrsJPOB
If test timings shift in the future, the unexpected requests could occur
during any test. Since there are many tests that use waitForFinishedRequest(),
any of them could start to fail intermittently at any point.
These changes fix other usages of wwaitForFinishedRequest() to include a
predicate that ignores the requests that are unexpected during the test.
MozReview-Commit-ID: Er0xyt3YBj6
The problem here is that the test expects to receive a request for the
|test-network-request.html| but the waitForFinishedRequest() accepts any
request that happens to occur at the same time. In this particular bug,
a GMP update is triggered during the test and the waitForFinishedRequest()
promise resolves with that particular request which obviously isn't the
one the test was expecting.
These changes add an optional predicate function parameter to
waitForFinishedRequest() which will be called for each completed request
and the returned promise only resolves when the predicate returns true for
a request.
Also, browser_console_netlogging.js begins to use the aforementioned
functionality by passing a predicate that only accepts the request for
|test-network-request.html| effectively fixing the intermittent failure.
MozReview-Commit-ID: AWhMRjrqP8i
Add a negative top offset to align swatches ( color, filter, bezier, ...) with
the values they represent.
MozReview-Commit-ID: 6EIQZ2UAHuc
--HG--
extra : transplant_source : %CF%E7%86%C7%90%DB%16%9B%E9%C4E%E0W%E7%87%07%CF%C9%F4%E4
Add a getProperties function to the animation actor to map KeyframeEffectReadOnly.getProperties
Call this new function in animation-detail and adapt the code as the structure
of the returned object structure is different from what getFrames returns.
Adapt a couple tests to the new object structure client-side, and a test server-side
to check getProperties returns what it should.
MozReview-Commit-ID: 2zKPEknukEK
Add a swatch before angle values in the rules panel and allow cycling
through angle units with shift+click (like we already do for color units).
MozReview-Commit-ID: CWhoUQTkP1G
--HG--
extra : transplant_source : %5B%E5%AD%22%D2%20uk%07%EE%A9%E4%91YS%B3R%C3%DF%21
This patch updates the Source Editor contextmenu's UX. Prior to the
patch, the menu would show the option "Add conditional breakpoint" even
when there was a conditional breakpoint. Now, that option reads "Edit
conditional breakpoint".
This patch updates the Source Editor contextmenu's UX. Prior to the
patch, the menu would show the option "Add conditional breakpoint" even
when there was a conditional breakpoint. Now, that option reads "Edit
conditional breakpoint".