| Age | Commit message (Collapse) | Author |
|---|
|
This will be used by the new EventTarget to check if it needs to do
special error event handling. Currently it isn't used for anything
else.
|
|
This fix this test262 test:
built-ins/JSON/stringify/value-string-escape-unicode.js
|
|
|
|
Per the CSSOM View spec, these are aliases for clientX and clientY.
|
|
We were chopping the top row of pixels off of the website favicons in
Browser's location editor. :^)
|
|
The current implementation of step 2a sort of manually implemented GetV
with a ToObject + Get combo. But in the call to Get, the receiver wasn't
the correct object. So when invoking toJSON, the receiver was an Object
type rather than a BigInt.
This also adds spec comments to SerializeJSONProperty.
|
|
Some over-eager copy-pasting led to incorrect code for the new chain.
|
|
Let's just use reference-counting pointers for this, even if it seems
safe not to.
|
|
This function was unnecessarily nested, which created a scenario where
we could get stuck in an infinite loop without advancing the
current_object pointer up the browsing context container chain.
|
|
Thanks to U9G for catching this! :^)
|
|
|
|
PropertyKey used to be called PropertyName, but got renamed. Let's
update all the variables of this type as well.
|
|
If the mousedown event hits something with is_focusable()==true,
we now update the document's focused element *instead* of placing the
text cursor at the focusable element.
This allows you to begin editing input elements by clicking them.
This feels very hackish and we'll need to come up with something nicer.
|
|
|
|
This mechanism feels rather awkward, but it's better than nothing.
|
|
This makes focus outlines show up in OOPWV at last! :^)
|
|
The main deviation from the spec is that we don't have a straightforward
representation of the spec's "focusable area" concept.
I've left a bunch of FIXME's around for our future selves. :^)
|
|
This is "currently focused area of a top level browsing context"
from the HTML spec.
|
|
These were being parsed, but skipped when rendering. With this fix, the
SVG on discord's invite screen looks pretty nice! :^)
|
|
Browser has a handy debug menu option to dump all stylesheets, so we
don't need to spam the console with this. (All the spam massively slows
down page loads.)
|
|
|
|
This was deprecated in favor of Core::Stream::TCPSocket, and now has no
users.
|
|
|
|
|
|
These pass now that negative zero is disallowed by SignedBigInteger.
|
|
If a big integer were to become negative zero, set the sign to instead
be positive. This prevents odd scenarios where users of signed big ints
would falsely think the result of some big int arithmetic is negative.
|
|
These were showing up in profiles.
|
|
We renamed the Frame class to BrowsingContext a while back, but forgot
to update some variable names.
|
|
Blowing up the debug console with a fajillion FIXME's whenever you
navigate in the web inspector is no fun.
|
|
Most of these errors mean that we will fail the job, but it won't crash
the application, at least.
|
|
As LibTLS now supports the Core::Stream APIs, we can get rid of the
split paths for TCP/TLS and significantly simplify the code as well.
Provided to you free of charge by the Core::Stream-ification team :^)
|
|
|
|
This commit converts TLS::TLSv12 to a Core::Stream object, and in the
process allows TLS to now wrap other Core::Stream::Socket objects.
As a large part of LibHTTP and LibGemini depend on LibTLS's interface,
this also converts those to support Core::Stream, which leads to a
simplification of LibHTTP (as there's no need to care about the
underlying socket type anymore).
Note that RequestServer now controls the TLS socket options, which is a
better place anyway, as RS is the first receiver of the user-requested
options (though this is currently not particularly useful).
|
|
The meaning of EOF depends on the underlying socket, but an empty slice
should terminate the buffering (otherwise we'd just spin forever).
|
|
This function used to sometimes return the entire input instead of the
value up to the delimiter, fix that and rewrite it to be a bit more
readable.
|
|
pending_bytes() and can_read_without_blocking() should also take
the buffered data into account, otherwise we'll end up pretending that
the socket cannot be read from while it has buffered data.
|
|
This is equivalent to Core::Socket::set_notifications_enabled(), and
serves to disable the on_ready_to_read() notifications, as the sockets
often implement these using the event loop, this method can help avoid
waking the event loop and spamming useless calls to on_ready_to_read().
|
|
|
|
And declare a few of the stream classes in the forwarding header.
|
|
|
|
|
|
This removes the duplicate code in
LocalServer::take_over_from_system_server and replaces it with
Core::take_over_accepted_socket_from_system_server.
|
|
release_fd() releases the fd associated with the LocalSocket it is
called on. This is analogous to release_value() on container objects in
AK, after which the object does not contain the value.
|
|
This functionality is required by Core::LocalServer and LibIPC depends
on LibCore.
take_over_accepted_socket_from_system_server has also been renamed to
take_over_socket_from_system_server as the socket need not be accepted
before taking it over. :^)
|
|
Gamma.h includes xmmintrin.h, which is X86-only. The file contains
code in other places that is compiled conditionally on __SSE__, so the
same macro is used to determine inclusion of the header.
|
|
We should no longer be generating empty fragments at the start and end
of an InlineNode, so we can drop this check.
|
|
|
|
These were incorrectly returning the content width and height of the
initial containing block. Also added spec links and comments.
|
|
This property represents the CSS content size, so let's reduce ambiguity
by using the spec terminology.
We also bring a bunch of related functions along for the ride.
|
|
|
