| Age | Commit message (Collapse) | Author |
|---|
|
Otherwise, the JS::Completion is always interpretted as an error by
ExceptionOr.
|
|
|
|
These are specified in the IDL as "unsigned long long", which translates
to u64.
|
|
Sadly, we don't have proper error propagation here. However, crashing
the Kernel just because a CDROM contains an invalid month seems like a
bad idea.
|
|
|
|
|
|
We'll throw it out automatically if some media query changes changes its
evaluation state in response to the resize, and that should be enough.
|
|
This was a fairly common source of unnecessary style invalidations.
|
|
After examination of all overriden Inode::traverse_as_directory methods
it seems like proper locking is already existing everywhere, so there's
no need to take the big process lock anymore, as there's no access to
shared process structures anyway.
|
|
The contents of the directory inode could change if we are not taking so
we must take the m_inode_lock to prevent corruption when reading the
directory contents.
|
|
All shared structures are already protected by "atomic" spinlocks for
those structures, so there's no need to take the big process lock.
|
|
All accesses to the mount table are already serialized by the actual
spinlock of that table.
|
|
This is not needed, because when we are doing this traversing, functions
that are called from this function are using proper and more "atomic"
locking.
|
|
This locking is simply not needed because the associated SysFS component
will use proper and more "atomic" locking on its own.
|
|
|
|
|
|
|
|
It does not make sense to test known-working code that is deprecated and
in the process of being removed. Also, this test becomes too cumbersome
to write without using read_all or line iteration in some form, and
migrating the test is just silly.
|
|
This starts working immediately in BFC thanks to calculate_inner_width
being used for width constraints. :^)
|
|
|
|
|
|
In order to support intrinsic size keywords (such as fit-content), we
need to be able to calculate the intrinsic sizes of any element, not
just those that form their own formatting context.
When a non-FC-root element is passed to calculate_some_intrinsic_size(),
we now create a synthetic BFC to handle sizing of them.
|
|
|
|
The marker bit is VP9-only, so move that into a new initialize_vp9()
function.
finish_decode() is VP9-only, so rename that to finish_decode_vp9().
|
|
...and keep a forwarding header around in VP9, so we don't have to
update all references to the class there.
In time, we probably want to merge LibGfx/ImageDecoders and LibVideo
into LibMedia, but for now I need just this class for the lossy
webp decoder. So move just it over.
No behvior change.
|
|
Introduces incomplete parsing of grid shorthand property. Only
<grid-template> part of syntax is supported for now but it is enough
to significantly improve rendering of websites that use this shorthand
to define grid :)
|
|
The path for floating, replaced elements must not fall through to the
path taken for floating, non-replaced elements. The former works like
inline replaced elements, while the latter uses a completely different
algorithm which doesn't account for intrinsic ratio. Falling through
overrides the correct value computed by the former.
Fixes #19061.
|
|
This fixes the issue when margin collapsing state was always reset if
a box has clear property not equal to none even if it does not actually
introduce clearance.
|
|
|
|
Makes 107 new tests pass in test262. :^)
|
|
|
|
|
|
This was crashing on google.com with the linux chrome user agent,
interestingly it seems like this behavior may have been accidental as
only two of the three `parse_number()` were changed in f7dbcb6
|
|
Ignore anonymous block boxes when resolving percentage weights that
would refer to them, per the CSS 2 visual formatting model
specification. This fixes the case when we create an anonymous block
between an image which uses a percentage height relative to a parent
which specifies a definite height.
Fixes #19052.
|
|
This is a normative change in the ECMA-262 spec. See:
https://github.com/tc39/ecma262/commit/25f9744
|
|
This proposal has been merged into the main ECMA-262 spec. See:
https://github.com/tc39/ecma262/commit/d95f42d
|
|
|
|
Implied point = point created by two subsequent "off curve" points.
Fixes following issues in function that builds glyph path from points:
- If first point is "off curve" it was wrongly treated as "on curve"
which caused wrong first point position in the path.
- If both first and last points in the path are "off curve" implied
point was not created between them which caused wrong path shape in
the end of the path.
|
|
fixes #18678
This is because the "From:" URL regularly overflows the line, leading
to an unreadable mess. Make sure that the labels for the widget
don't wrap as well, as the widget is fixed height and width.
|
|
This makes cross-origin image loads actually see the MIME type the
server tells us. :^)
|
|
|
|
|
|
If some page throws "display: ruby-text" or some such at us, let's just
complain and carry on.
|
|
If CSS requests a font that we have loaded, but we didn't associate it
with a specific weight and/or slope, let's still use it if it matches
the family name.
This is a hack until we implement proper CSS font selection.
|
|
This corresponds to the `<custom-ident>` type in CSS grammar.
|
|
|
|
|
|
This allows us to free entire chains of blocks in one go.
|
|
The free block list now gets populated on opening a database file.
Ideally we persist this list inside the heap itself, but for now this
prevents excessive heap growth.
|
|
When overwriting existing heap storage that requires fewer blocks, make
sure to free all remaining blocks so they can be reused in the future.
|
