The algorithm now generates q-value 0.9 for second language in two language option. Now q-weight of each language decrements by 0.1 (minimum 0.1) down the language list.
Differential Revision: https://phabricator.services.mozilla.com/D273761
While reverting all the work related to cross platform escaping of curl (See Bug 1976589), i tried to cleanup the
escaping of new line characters, but introduced carriage returns (\r).
This patch reverts back to the original fix from Bug 1968414
Differential Revision: https://phabricator.services.mozilla.com/D265397
While reverting all the work related to cross platform escaping of curl (See Bug 1976589), i tried to cleanup the
escaping of new line characters, but introduced carriage returns (\r).
This patch reverts back to the original fix from Bug 1968414
Differential Revision: https://phabricator.services.mozilla.com/D265397
Detect CSS variables in parseDeclarationsInternal instead of using SharedCssLogic.isCssVariable.
Consider CSS variables name always valid so we avoid expensive calls to InspectorUtils.supports().
Differential Revision: https://phabricator.services.mozilla.com/D258853
This patch reverts important parts of D243110 related to Bug 1950001
This goal is for the Copy As Curl(Windows) to work properly on just the windows CMD
Differential Revision: https://phabricator.services.mozilla.com/D255793
Migrate associated test to check the getCSSVariables util function, that was used
in `hasCSSVariable` and is still used in other parts of the code, so we keep
some coverage.
Differential Revision: https://phabricator.services.mozilla.com/D257467
This patch reverts important parts of D243110 related to Bug 1950001
This goal is for the Copy As Curl(Windows) to work properly on just the windows CMD
Differential Revision: https://phabricator.services.mozilla.com/D255793
This consolidates the jest environment definition, and the xpcshell globals into the devtools/.eslintrc.mjs file, for easier configurations.
It also changes the restart of the configurations to work with flat config.
Differential Revision: https://phabricator.services.mozilla.com/D249948
Create a dummy rule with the content of the rule being modified so we can
check if it has a nested rule. In such case, we can then get the location
of the nested rule so we can insert the added text in the correct position.
A few unit test cases are added to make sure the RuleRewriter does handle
nested rules properly.
Differential Revision: https://phabricator.services.mozilla.com/D237734
Stop collecting declarations as soon as we detect a nested rule.
Any declaration that come after the nested rules are now put in a
separate CSSNestedDeclaration rule.
We still need to handle the nesting logic for commented declarations,
as highlighted by a test case in test_parseDeclarations.js.
Other test cases there for nested rules are updated, and we add
a CSSNestedDeclaration in a Rules view mochitest to make sure we
don't get the declaration in the "top level" rule anymore.
Differential Revision: https://phabricator.services.mozilla.com/D237520
Use a grid for the tooltip, driven by CSS variables that we retrieve in JS
to compute the canvas size.
Retrieve CSS variables for drawing in the canvas, and draw the diagonal
between the control points in the canvas too (instead as a background gradient).
Don't overlap the canvas and the animation easing preview as it could be
hard to discernate in High Contrast Mode.
Fix a couple issues with RTL languages.
Differential Revision: https://phabricator.services.mozilla.com/D227174
This adds different nested state so we can simply ignore nested CSS rules.
I added a lot of different test cases in the existing `parseDeclarations`
unit test so we can have good coverage.
It also removes "{" from `CSS_BLOCKS` as this wasn't something that could happen
before nesting, and we're handling that separately.
We took this as an opportunity to put opening brackets in `currentBlocks` instead
of closing ones, as it's a bit easier to understand.
Differential Revision: https://phabricator.services.mozilla.com/D180701
Seeing those offsets integer in the test case is a bit hard to assert that they
do actually refer to the expected part of the input.
This adds a `declarationText` property on the expected object that can be used
to properly asserts produced offsets.
Differential Revision: https://phabricator.services.mozilla.com/D181094
The existing xpcshell test is not a good fit for testing a UI widget such as the VariablesView
Migrate to a browser mochitest and restore usage of document.l10n.setAttributes initially added in Bug 1830679
Differential Revision: https://phabricator.services.mozilla.com/D181096
This adds an authoring tool similar to the one we have for cubic bezier.
A swatch is added next to `linear()` functions and clicking on it will show
the widget.
Modifying the line in the widget will update the value of the `linear()` function
in the rule view.
Differential Revision: https://phabricator.services.mozilla.com/D153333
Make the callsites call InspectorUtils.rgbToColorName instead.
Since it was throwing when passed a non-valid named color,
which wasn't the expected outcome in DevTools, modify the
c++ method so it return an empty string instead.
Add a dedicated test since there wasn't one.
Differential Revision: https://phabricator.services.mozilla.com/D168989
Make the callsites call InspectorUtils.rgbToColorName instead.
Since it was throwing when passed a non-valid named color,
which wasn't the expected outcome in DevTools, modify the
c++ method so it return an empty string instead.
Add a dedicated test since there wasn't one.
Differential Revision: https://phabricator.services.mozilla.com/D168989