Age | Commit message (Collapse) | Author |
|
|
|
|
|
This parses Blocks.txt for CharacterType properties and creates
a global display array for use in apps.
|
|
If we try to <link> a stylesheet that was already cached, we'll get a
synchronous resource_did_load() callback. Because of this, it's
necessary to set up the document load event delayer *before* calling
set_resource(), as otherwise we'd be stuck without a load event forever.
|
|
If we try to @import a stylesheet that was already cached, we'll get a
synchronous resource_did_load() callback. Because of this, it's
necessary to set up the document load event delayer *before* calling
set_resource(), as otherwise we'd be stuck without a load event forever.
|
|
This ensures that the layout information is current, even when the
scroll request happens immediately upon page load.
This fixes an issue where reloading ACID2 wouldn't scroll down to the
"#top" anchor point.
|
|
|
|
This fixes an issue with the eyes on ACID2 not appearing until the
page is repainted after loading.
|
|
|
|
Add icon and tooltip to 'Functions Help' button.
|
|
Add icons where they are missing.
|
|
|
|
10C80-10CFF https://www.unicode.org/charts/PDF/U10C80.pdf
|
|
1F7CC, 1F7D0, 1F7D5-1F7D8, 1F7F0, 1F780-1F783
https://www.unicode.org/charts/PDF/U1F780.pdf
|
|
1F6A9, 1F6AA, 1F6AB, 1F6B9, 1F6BF, 1F6C6, 1F6C7, 1F6CF, 1F6E1, 1F6E3,
1F6F7, 1F6A1, 1F6F6, 1F6F8, 1F6A0, 1F69D, 1F69E, 1F69F, 1F682, 1F683,
1F6A2
https://www.unicode.org/charts/PDF/U1F680.pdf
|
|
1F67C-1F67F, 1F67A, 1F676-1F679, 1F672, 1F673, 1F670
https://www.unicode.org/charts/PDF/U1F650.pdf
|
|
1123A, 1123B https://www.unicode.org/charts/PDF/U11200.pdf
|
|
108E0-108FF https://www.unicode.org/charts/PDF/U108E0.pdf
|
|
0ED0 https://www.unicode.org/charts/PDF/U0E80.pdf
|
|
This is way more useful then the default "Open with" option which
is Text Editor.
|
|
10CD1E (Yakmeasure), 10CD1F (Yakcowboy), 10CD20 (Yakspeed),
10CD21 (Yakmando)
|
|
Inserts icons for 'Export', 'Add Track' and 'Next Track'.
|
|
We needed to propagate the forbidden token set to all parsing functions
that can call back into parse_expression.
|
|
|
|
In some cases the height of the parent is needed in computations
of the height for the child. This patch attempts to fix these cases.
|
|
The icons for these actions were added in a previous commit but never
used, now they are.
|
|
Implements 'Merge Active Layer Up' and adds it to the 'Layer' menu.
|
|
|
|
This allows BFC to position all absolutely positioned descendants in the
same pass.
|
|
|
|
This doesn't send the correct type of click event, but it does send
something, so it's already somewhat useful. :^)
|
|
|
|
This matches the spec terminology around the "stack of open elements".
|
|
|
|
|
|
Before this was a mix of different strategies but copy_data_properties
does all of that in a spec way.
This fixes numeric properties in object spreading. And ensures that any
new properties added during spreading are not taken into account.
|
|
A common use case in JS is pushing items in an array in a loop.
A simple test case of 100_000 pushes took around ~20 seconds.
This is due to the fact that any pushed element per definition is beyond
the current size of the array. This meant calling grow_storage_if_needed
which then grew the storage by 25%. But this was done on every single
push, growing the array just a little bigger than its current capacity.
Now we now first use capacity of the array and only grow if the array
is actually full.
This decreases the time for 100_000 to around 0.35 seconds.
One problem is that we never shrink the capacity of the array but this
was already an issue before this.
|
|
This is no longer needed as BrowsingContextContainer::content_document()
now does the right thing, and HTMLIFrameElement.contentDocument is the
only user of this attribute. Let's not invent our own mechanisms for
things that are important to get right, like same origin comparisons.
|
|
|
|
Check of domains is left as a FIXME as our Origin class doesn't support
those yet.
|
|
The HTML Origin spec has two similar but slightly different concepts of
origin equality: "same origin" and "same origin-domain". Let's be
explicit with the naming here :^)
Also add spec comments.
|
|
This is what the HTML Origin spec calls it.
|
|
With the spreadsheet:
```
A0:1
B0:2
A1:2
B1:3
```
Before: sum(range("A0","B1")) === 3
After: sum(range("A0","B1")) === 8
|
|
|
|
https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#cother-other-default-operation-rules
"The compiler is more likely to get the default semantics right and
you cannot implement these functions better than the compiler."
|
|
This should hopefully resolve a clang ICE seen in PR #12523.
|
|
The spec version of canonical_numeric_index_string is absurdly complex,
and ends up converting from a string to a number, and then back again
which is both slow and also requires a few allocations and a string
compare.
Instead this patch moves away from using Values to represent canonical
a canonical index. In most cases all we need to know is whether a
PropertyKey is an integer between 0 and 2^^32-2, which we already
compute when we construct a PropertyKey so the existing is_number()
check is sufficient.
The more expensive case is handling strings containing numbers that
don't roundtrip through string conversion. In most cases these turn
into regular string properties, but for TypedArray access these
property names are not treated as normal named properties.
TypedArrays treat these numeric properties as magic indexes that are
ignored on read and are not stored (but are evaluated) on assignment.
For that reason there's now a mode flag on canonical_numeric_index_string
so that only TypedArrays take the cost of the ToString round trip test.
In order to improve the performance of this path this patch includes
some early returns to avoid conversion in cases where we can quickly
know whether a property can round trip.
|
|
The existing implementation, which is used by Node::hit_test() and
sub-classes, does not include stacking contexts which prevents hit
testing from returning elements contained by those stacking contexts
in some situations.
This is quite rough and definitely not optimal. The stacking contexts
are not retrieved in the correct order. They should be sorted by
z-index then tree order.
This change makes DuckDuckGo technically usable with all the absolute
and relative positioning they use.
|
|
For PNG color type 2 (TrueColor), if there's a tRNS chunk, it specifies
an R/G/B triplet in the image bit depth. This triplet acts as the
transparency value, and should yield transparent pixels wherever that
specific color value is present.
We now support this. :^)
|
|
The tRNS metadata is valid for color types 0, 2 and 3, so let's collect
it in each of those cases.
This ensures that we produce a bitmap with an alpha channel if needed.
|