| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
It was named "fragment" mainly because I added it back when there was
still a separate InlineBox type and I needed another name.
Now InlineBox is gone, and I'm tired of typing fragment.
|
| |
|
|
|
|
|
|
| |
* fix clip for image
* switch back img's display to inline
* fix image width calculation without specified width/height
I'm not 100% sure if this is correct, but it certainly looks better.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Overflow pretty much requires scrollbars, but those wouldn't work in
dump mode, plus of course they would be a pain to implement. So as a
simple alternative:
* overflow: hidden, clip works as per spec.
* overflow: auto, overlay, scroll invert the intrinsic minimum size
clamping logic instead of adding a scrollbar.
What this concretely means, is that this
<pre style="overflow: scroll; height: 1em">
test
test
test
</pre>
will, instead of creating a scroll container, just override the
specified height.
This hack works surprisingly well, because CSS pretty much requires
setting height on scroll containers, so authors aren't incentivized to
set height on the parent container too (because the contents are already
sized appropriately).
One issue left is how to deal with overflow: hidden ancestors. For now,
I've made it so that it can spill for overflow-x, and always clips
on overflow-y, because it's much less likely to bleed into other
text horizontally than vertically. But there is definitely room
for improvement, e.g. we could track space requested by scrolling
children and expand parent boxes based on that.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Necessary for flex. Previously we just used the actual height, but that
didn't account for boxes that size themselves depending on the available
height (mainly just images for now).
This also irons out intrinsic min width calculation somewhat, squashing
several bugs.
I hope it works well. It is a significant change in size calculation,
so maybe there are still new bugs lurking.
|
| |
|
|
| |
Lets us skip a couple pointless multiplications/divisions during layout.
|
| |
|
|
|
| |
The test case attached is undefined in CSS 2.1, but css-sizing-3
wants us to just ignore the width property (I think).
|
| |
|
|
|
|
|
| |
this is necessary too, now that I think of it
(well, table caption sizing is still half-broken, but that's a problem
for another day...)
|
| | |
|
| |
|
|
|
| |
If the contents are larger than the specified cell height, then it is
simply ignored.
|
| |
|
|
|
|
| |
using div instead of / is sort of weird, but it makes it clearer if
we're dividing floats or layoutunits (and is already what the code
uses).
|
| |
|
|
|
| |
"Computed" was redundant; other types of values don't have a common
type.
|
| | |
|
| |
|
|
| |
We can do this now that xminwidth is more accurate.
|
| |
|
|
| |
better
|
| |
|
|
| |
still not quite right, but it's slowly taking shape
|
| |
|
|
| |
yeah idk
|
| |
|
|
|
| |
Seems more compatible with websites that use smaller fonts + padding
for styled code tags.
|
| |
|
|
|
|
|
|
| |
Gets rid of rounding errors when positioning images.
Theoretically this is possible with Sixel too, but as always, it's
ten times as difficult to implement as with Kitty, so I'll leave it
for later.
|
| |
|
|
|
|
|
|
| |
Roughly halves the object's size, and gets rid of a large number of
allocations.
It could be compressed further into a bitmap, but I'm not sure if it's
worth the complexity.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
ugly, but better than the status quo.
the core issue is that width, min-width should clamp xminwidth too, but
it doesn't. this hadn't been an issue until recently, but since I made
<pre> stretch out xminwidth too it had the unfortunate result that you
now have to scroll on pages that nest pre in a flex.
this still isn't a proper fix, in particular it won't work if min-width
is set to 0, but on the sites I tried it happens to work anyway.
|
| |
|
|
|
|
|
|
| |
Probably a remnant from back when startOffset meant (and was used for)
something different.
Interestingly, there was already a test case for this, but it was also
wrong.
|
| |
|
|
|
| |
This couldn't get into system.nim for technical reasons, but it's still
pretty useful when iterating over non-mutable openArrays.
|
| | |
|
| | |
|
| |
|
|
| |
forgot about word-break
|
| |
|
|
|
|
|
| |
This broke CJK combined with table layouts.
(Inline layout's state dependencies between procs are getting a bit
scary...)
|
| | |
|
| |
|
|
| |
maybe I'll get it right one of these days
|
| |
|
|
|
| |
The rowspan filler must get a smaller colspan if its first cells are
occupied by another cell with a colspan > 1.
|
| |
|
|
|
|
|
| |
far from perfect, but it's something.
(ideally, we should store enums in a bitmap instead of allocating a
GC'ed property for each of them.)
|
| | |
|
| |
|
|
| |
like line height, this caused more trouble than it was worth
|
|
|
as much as I wish it weren't, layout *is* css.
|