| Age | Commit message (Collapse) | Author |
|---|
|
Previously the color blending and alpha blending were working from
opposite sides.
|
|
|
|
This is just a quick test that everything is working. Currently
it paints the gradients with the existing
painter.fill_rect_with_gradient(). This can only handle two-color
orthogonal gradients.
|
|
|
|
This should parse linear-gradient()s as defined in the W3 spec
https://drafts.csswg.org/css-images/#linear-gradients.
Note: This currently cannot parse multi-position color stops,
these are shown on MDN and work in Firefox and Chrome, though do
not seem to be defined in the spec.
See: https://developer.mozilla.org/en-US/docs/Web/CSS/gradient/linear-gradient#gradient_with_multi-position_color_stops
P.s. This also allows -webkit-linear-gradient for compatibility.
|
|
|
|
This moves the logic from ColorStyleValue::to_string() to a standalone
function.
|
|
Step 19 of node removal was missing, which allows the mutations of the
descendants of the removed node to still be observed by the parent.
Step 20 of node removal queued the mutation record for the removed
node instead of it's parent. Since queuing takes place after the node
is removed from the tree, the mutation record would be lost as the only
inclusive ancestor of the node at this point is only the node itself.
|
|
This object contains all the CSS "used values" as seen during the layout
process, so calling it "used values" seems appropriate. :^)
|
|
This seems a bit more descriptive (and also a bit shorter).
|
|
We currently ignore the `align-content` property, that's a FIXME
for our future selves.
|
|
The CSSWG draft Flexbox spec is a bit clearer on some details, so let's
update our implementation to match the latest version.
|
|
|
|
Previously, changing a system theme with Calculator opened made buttons
with custom color not to update to the new theme - the background color
remained from the previous one.
This is because when setting the color, the widget has to copy the
current palette and modify the foreground color there, which means it
will no longer refer to the system theme and any change there will not
happen here.
Using colors from a system palette fixes this issue and makes buttons
look slightly different from what was here before. But that is because
they're now somewhat more integrated with the system themes! :^)
Type | Old color | New color role
---- | --------- | --------------
Numbers | "blue" | SyntaxNumber
Functions (sqrt, %) | "blue" | SyntaxFunction
Operators (+ - * /) | text-default | SyntaxOperator
Backspace, CE and C | "brown" | SyntaxControlKeyword
Memory operators, = | "red" | SyntaxPreprocessorValue
|
|
|
|
When |& is typed, stderr will be piped to stdout before the actual
piping happens. This behaves basically like a 2>&1 | (and the
underlying implementation transforms it to that anyway).
|
|
Previously we would erroneously apply the stylization to the whoever
called stylize next. Now we first check whether the span is non-empty
before stylizing. All non-empty spans must have at least one character
in them (end-exclusive).
|
|
|
|
|
|
|
|
|
|
See: https://github.com/tc39/ecma262/commit/5f31dd6
|
|
Makes it much easier to scroll through the file while comparing to the
spec. Proposals are inserted alphabetically as that's where they will
likely end up once merged into the main spec.
|
|
Makes it much easier to scroll through the file while comparing to the
spec. Proposals are inserted alphabetically as that's where they will
likely end up once merged into the main spec.
|
|
|
|
|
|
|
|
This was a leftover from when ComputedValues stored sizes in Optionals.
Now that we've gotten rid of the "undefined" state, there's no need for
this helper, we can just access the size values directly.
|
|
Since we re-use this value later in the layout algorithm, we have to
update it before leaving the "resolve flexible lengths" step.
|
|
Previously the text would be up close to the left / right border
depending on the alignment.
This patch increases the padding on either side from one to four pixels.
|
|
|
|
This is a quick and dirty fix to at least get the Inspector working
again. This is a very bad solution long term, because it will spin on
the EventLoop. That is why there is a message reminding everyone this
problem still needs to be fixed, every time this is actually done.
|
|
|
|
WidgetGallery is only a demo anyways, and the perfect target to test the
Inspector.
|
|
The color slider on the ColorPicker widget's "Custom Color" page will
now update when changing the color with the individual channel
spinboxes and the larger color field box.
Fixes #14425
|
|
|
|
|
|
This brings the spacing in line with the rest of the system, and
removes unneeded margins that only bloated the layout and caused edges
to be misaligned.
|
|
These changes bring the margins, spacing, and sizes more in line with
what is used in the rest of the system.
|
|
|
|
Those inconveniences come from cursor and selection not being saved
during the switch.
|
|
The function converts Key_[Up, Down] to the corresponding
VerticalDirection.
|
|
|
|
For example, consider the locales "en-u-nu-fullwide" or "en-u-nu-arab".
The CLDR only declares the "latn" numbering system for the "en" locale,
thus ResolveLocale would change the locale to "en-u-nu-latn". This patch
allows using non-latn numbering systems digits.
|
|
This has been superseded by get_preferred_keyword_value_for_locale,
which doesn't require allocating a Vector just to return its first
element.
|
|
Working around not having collation data in the CLDR now handled in the
Unicode generators.
|
|
|
|
|
|
This also ensures we only include values we actually support in the
generated list of available values.
|
|
|
