| Age | Commit message (Collapse) | Author |
|---|
|
- U+10CD24 Yakslow
- U+10CD25 Buffyak
- U+10CD26 Yaktrap
- U+10CD6A Yakthink
- U+10CD6B Hyperyakkie
|
|
🧔♀️ - U+1F9D4 U+200D U+2640 WOMAN: BEARD
🧝♂️ - U+1F9DD U+200D U+2642 MAN ELF
🧗 - U+1F9D7 PERSON CLIMBING
🦕 - U+1F995 SAUROPOD
🦖 - U+1F996 T-REX
💱 - U+1F4B1 CURRENCY EXCHANGE
🌬️ - U+1F32C WIND FACE
|
|
⚧️ - U+26A7 TRANSGENDER SYMBOL
|
|
2264-2265 https://www.unicode.org/charts/PDF/U2200.pdf
|
|
The combination of template + auto&& parameter + constexpr if statements
allowed one caller to pass in a GlobalObject, without the compiler
complaining.
|
|
|
|
|
|
For whatever reason, web pages sometimes add and/or remove a completely
empty style sheet. When this happens, we don't need to invalidate the
document's style, since the outcome will be the same as before.
|
|
These helper documents don't actually get rendered, so computing style
and doing layout for them is a complete waste of work.
|
|
HTML template elements don't affect rendering, so invalidating the
entire document's layout after poking into a <template> was a huge waste
of work on template-heavy pages.
|
|
There's no need to force a synchronous relayout after the viewport has
been resized. By making it lazy, we might be able to coalesce it with
other layout work.
|
|
Like for attribute changes, we now only invalidate the insertion parent
and all of its descendants. Again, this is very aggressive, but also
way less than doing the entire document.
Once we implement the CSS :has() selector, we'll need to become more
sophisticated about invalidation.
|
|
This was moved from HTMLTemplateElement to Document at some point,
so let's match the spec and move it here too.
|
|
We now only invalidate the style of the context element and all of its
descendants. It's still very aggressive, but much less than before.
Note that this will need to become a lot smarter once we implement the
CSS :has() selector.
|
|
This patch adds inline spec comments, and then adjusts the code a bit
so it reads more like the spec.
|
|
|
|
This is a stopgap until we implement shorthand -> longhand conversion.
|
|
|
|
|
|
|
|
This has the exact same validation as memory.fill
|
|
YouCompleteMe is a plugin for Vim which provides code-completion
functionality. This change adds a configuration file which makes
YouCompleteMe aware of which compile flags to use with clangd.
|
|
|
|
|
|
This commit adds a trans emoji
|
|
|
|
This reverts commit dc15cacfc3d0b26923659b619f74d02a4e6516bd.
It appears to be causing some assertions, so let's revert it.
|
|
QEMU 7.1 was released on August 30th.
Release Notes: https://wiki.qemu.org/ChangeLog/7.1
The patch 'Toolchain/Patches/qemu-cf-protection-none.patch' (or similar)
has been upstreamed so it can be safely removed.
|
|
|
|
Emoji added:
🐘 - U+1F418 ELEPHANT
|
|
Previously, this would cause an assert to fail if one reads a completely
buffered line into a buffer that is smaller than the Stream's internal
buffer.
|
|
For convenience, `DisjointIntRectSet` is an alias for
`DisjointRectSet<int>`, and is used everywhere for now.
|
|
This is in preparation for converting it to a template. No changes here,
only moving code around.
|
|
This looks like a copy-paste issue from Rect::to_string().
|
|
Line, Point, Rect, and Size now all have Formatters that will work with
any type that itself has a Formatter.
|
|
We were neglecting to resolve the used horizontal padding and border
properties on block-level boxes when treating their width as `auto`
during intrinsic sizing.
This led to padding and border not contributing to the intrinsic width
of their containing block
|
|
This ensures that static position calculations has access to final
box offsets.
|
|
|
|
We currently have two build-time parsers for the UCD's emoji-test.txt
file. To prepare for future changes, this removes the Bash parser and
moves its functionality to the newer C++ parser.
|
|
|
|
Vectorscope and Histogram are now hidden by default. New menu "Scopes"
allows for them to be toggled on/off.
|
|
|
|
This is intended to reflect the POSIX sched_setparam API, which has some
cryptic language
(https://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_08_04_01
) that as far as I can tell implies we should prioritize process
scheduling policies over thread scheduling policies. Technically this
means that a process must have its own sets of policies that are
considered first by the scheduler, but it seems unlikely anyone relies
on this behavior in practice. So we just override all thread's policies,
making them (at least before calls to pthread_setschedparam) behave
exactly like specified on the surface.
|
|
|
|
|
|
The priority range was changed several years ago, but the
userland-reported limits were just forgotten :skeleyak:. Move the thread
priority constants into an API header so that userland can use it
properly.
|
|
|
|
The syscalls are renamed as they no longer reflect the exact POSIX
functionality. They can now handle setting/getting scheduler parameters
for both threads and processes.
|
|
We were lucky until now that nobody included both headers that have a
definition for this (identical) struct.
|
|
|
