| Age | Commit message (Collapse) | Author |
|---|
|
This commit also removed the redundant `filename` parameter from
`GLContextWidget::load_file`, since the filename is already stored
within the file itself.
|
|
|
|
|
|
|
|
|
|
|
|
The current implementation is a bit of a hack since we also want to keep
around the previous variants for now, but will be cleaned up later once
all applications have been ported to the new API.
|
|
Previously when opening a crash report for HackStudio, the
`unveil("/bin/HackStudio", "rx")` call was failing because of the
earlier `unveil(executable_path.characters(), "r")` call requesting only
"r" permissions for it. This patch handles this specific case, so you
can crash HackStudio to your heart's content. :^)
Also, we were unveiling the executable path twice, once manually and
once implicitly as part of the coredump's libraries, so we now check for
the latter and avoid it.
Thanks to Daniel for noticing what was right in front of me and I didn't
see!
Co-authored-by: Daniel Bertalan <dani@danielbertalan.dev>
|
|
|
|
|
|
|
|
Tweak silver theme to look even more like Mac OS 9
|
|
Add Olive theme
|
|
|
|
|
|
We were returning row-major matrices when OpenGL clients are expecting
column-major instead.
|
|
|
|
|
|
This prevents overwriting the front face mode when providing `GL_BACK`
as a parameter.
|
|
|
|
|
|
|
|
In case when the PCI class, device or vendor is unknown, show
that it is unknown instead of just putting the ID
|
|
|
|
|
|
3041-309F https://www.unicode.org/charts/PDF/U3040.pdf
|
|
4E06, 4E07, 524D, 56FA, 56D7-56E0, 6708
https://www.unicode.org/charts/PDF/U4E00.pdf
|
|
|
|
Despite looking like it was still needed, it was only used for passing
to other calls to Length::resolved() recursively. This makes the
various `foo.resolved().resolved()` calls a lot less awkward.
(Though, still quite awkward.)
I think we'd need to separate calculated lengths out to properly tidy
these calls up, but one yak at a time. :^)
|
|
All `<percentage>`s in the CSS grammar are now represented by the
`Percentage` class, and `<length-percentage>` by `LengthPercentage`.
|
|
|
|
A lot of this is quite ugly, but it should only be so until I remove
Length::Type::Percentage entirely. (Which should happen later in this
PR, otherwise, yell at me!) For now, a lot of things have to be
resolved twice, first from a LengthPercentage to a Length, and then
from a Length to a pixel one.
|
|
The flexbox logic confuses me so regressions are possible, though our
test page looks the same as before so it should be fine.
Renamed FlexBasis::Length -> LengthPercentage too, for clarity.
|
|
Not much needed changing this time, hurrah! :^)
|
|
|
|
This was only ever used in order to set the m_font_size for another
Node, so it can just go. :^)
|
|
This does undo the changes in 88c32836d858564a8664f0fc85f8fd36021945bf,
which accounted for our bitmap fonts being a different size than the
`font-size` property requests. I think this would be better handled
inside Length::to_px(), which would then apply to all font-size-relative
lengths (eg, em and rem) instead of only for the line-height property.
|
|
Both of these have "auto" as their initial value, so the only reason
they work currently is that "auto" is implicitly a Length.
|
|
Checking these for `auto` is awkward, but separating that will come
later. :^)
|
|
The visit_lengths() code is a bit awkward but we'll clean that up later.
|
|
Layout::Node still treats border radii as having a single value instead
of horizontal and vertical, but one less hack is nice, and helps with
conversion to LengthPercentage. :^)
|
|
This is a guinea pig. So far so good?
|
|
|
|
This is in a slightly weird state, where Percentages are sometimes
Lengths and sometimes not, which I will be cleaning up in subsequent
commits, in an attempt not to change all of LibWeb in one go. :^)
|
|
|
|
Length and Percentage are different types, and sometimes only one or the
other is allowed in a given CSS property. This is a first step towards
separating them.
|
|
This mirrors the cases in `built-ins/JSON/parse/text-negative-zero` in
test262
|
|
Regardless of the backing type that the number would otherwise parse to,
if it is zero and the sign was supposed to be negative then it needs to
be a floating point number to represent the correct value.
|
|
This is in line with this recent change to Conditional-3:
> Removed the “unknown” value in CSS feature queries’ boolean logic,
> defining unrecognized syntaxes as “false” instead.
> https://github.com/w3c/csswg-drafts/issues/6175
|
|
|
