| Age | Commit message (Collapse) | Author |
|---|
|
The primary benefit of this is that it's unsigned, as you can't have a
negative amount of children. Plus, all the users of child_count expect
it to be size_t.
|
|
|
|
Range's member variables are stored in AbstractRange as per the spec,
as they are also shared with StaticRange.
|
|
This creates an Audio element with preload="auto" and the given src
attribute.
Required by Cookie Clicker.
|
|
1% progression on ACID3. :^)
|
|
Clang doesn't like unused lambda captures.
|
|
This resolves #12766 which occurred when the user tried to
use either the cut or copy action before selecting a cell.
|
|
We now validate that the provided tag names are valid XML tag names,
and otherwise throw an "invalid character" DOM exception.
2% progression on ACID3. :^)
|
|
Since we now honor the CSS font-size values when deciding line box
metrics, we sometimes find ourselves needing to paint text with a bitmap
font into a box that isn't large enough for the glyphs.
As it turns out, it looks a bit better if we just grow the paint rect to
fit the glyphs (instead of painting chopped-off glyphs.) So let's just
do that for now.
|
|
If vertical-align is a length value, we lift each line box fragment that
far from the baseline of the line box.
This is rather messy, and we'll have to improve factoring as we add
support for more alignment types.
|
|
The purpose of "entering" a box is to collect box model metrics that
apply to content fragments within the box. However, inline-blocks are
special, in that their inner content does not directly participate in
the inline formatting context outside it.
|
|
We were neglecting to pop nodes from the box model stack. The metrics
were already being zeroed out when used, but let's not grow the stack
needlessly.
|
|
This will allow us to support more kinds of vertical alignment.
|
|
|
|
Instead of just the outline, fill them with some semi-transparent color.
Also add tag name, ID, classes and coordinates to the little tooltip.
Finally, use the border box instead of the context box for metrics,
same as other browsers.
|
|
Instead of awkwardly visiting and mutating lengths inside StyleValues,
we now simply create a new StyleValue instead.
This fixes an issue where inherited relative lengths could get
absolutized using a parent as reference, and then not having the correct
values when used in a child context.
|
|
|
|
|
|
This was done with CLion's automatic rename feature.
|
|
This was done with CLion's automatic rename feature.
|
|
Rename NotificationServerConnection=>ConnectionToNotificationServer.
This was done with CLion's automatic rename feature.
|
|
Rename ClipboardServerConnection=>ConnectionToClipboardServer.
This was done with CLion's automatic rename feature.
|
|
Also renames ServerConnectionWrapper=>ConnectionToServerWrapper
and ServerConnectionInstances=>ConnectionToServerInstances
This was done with CLion's automatic rename feature.
|
|
This was done with CLion's automatic rename feature.
|
|
Rename WindowManagerServerConnection=>ConnectionToWindowManagerServer.
This was done with CLion's automatic rename feature.
|
|
This was done with CLion's automatic rename feature.
|
|
This was done with CLion's automatic rename feature and with:
find . -name ClientConnection.h
| rename 's/ClientConnection\.h/ConnectionFromClient.h/'
find . -name ClientConnection.cpp
| rename 's/ClientConnection\.cpp/ConnectionFromClient.cpp/'
|
|
1% progression on ACID3. :^)
|
|
1% progression on ACID3. :^)
|
|
Note that we implement .elements as a HTMLCollection for now, instead of
the correct HTMLFormControlsCollection subclass. This covers most
use-cases already.
1% progression on ACID3. :^)
|
|
This API now follows the spec a bit more closely, with regards to the
event being dispatched. There are still FIXME's but this is already an
improvement.
2% progression on ACID3. :^)
|
|
|
|
|
|
This matches how other implementations behave.
1% progression on ACID3. :^)
|
|
|
|
This makes <style> elements reparse the CSS when their text child is
programmatically changed.
|
|
1% progression on ACID3. :^)
|
|
There were two things preventing this from working right:
- UIEvents::UIEvent::create() was actually just DOM::Event::create()
- We didn't return the right JavaScript wrapper type for UIEvent
|
|
Previously we were only matching elements with *no* text children.
With this patch, we now also allow any number of empty text children to
be present as well.
1% progression on ACID3. :^)
|
|
1% progression on ACID3. :^)
|
|
This allows you to split around a custom separator, and enables
expressive code like this:
string.split_view(is_ascii_space);
|
|
The rightmost edge of the available space ends exactly at the leftmost
right-side floating box, not one pixel away from it.
|
|
Use the new Gfx::Font::AllowInexactSizeMatch parameter when doing CSS
font lookups. This fixes a long-standing issue where text with e.g text
with "font-size:12px" would be larger than "font-size:13px" since there
was an exact match for 12, but none for 13 (so we'd fall back to 10).
|
|
This allows bitmap font lookup to return the best matching size instead
of failing completely. The previous behavior (exact matches only)
remains the default.
|
|
Instead of re-measuring the distance between the left and right edges of
a line box, we now simply adjust the final width based on how much the
rightmost fragment moved during the alignment process.
|
|
|
|
Uses the new Window FrameShape. Fixes some erroneously elided text
and incorrect calendar window placement.
|
|
Uses the new Window FrameShape. Fixes margins for erroneously
elided CheckBoxes. Demystifies the numbers used to calculate the
slider window rect.
|
|
This shape is for use by the main widget of a frameless window
that still wishes to have proper borders but no title.
Raised Containers were used previously for this pattern but did not
always represent perspective and shadow correctly depending on thread
highlighting and the immediate background color. Containers are
really meant to be used inside other widgets where the background
color can be controlled.
|
|
These were added 3 years ago but never used. Their intended purpose
was probably superceded by the Separator widget.
|
