| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
yay!!!!
* Add support for float: left, float: right
Also, misc stuff:
* Add support for display: flow-root
* Set line width to the maximum allowed width on line wrap
* Various refactorings
Still todo: support clear
|
|
|
|
|
|
|
|
|
| |
* Blocks are now positioned before their text contents would be
layouted
* Untangle calcAvailableSpaceSizes's results from BlockBox
* Move a couple of objects from box -> engine
* Use Size in a few more places
* Set display to block if float is not none
|
|
|
|
| |
merge positionBlocks with buildBlocks
|
|
|
|
|
|
| |
* remove Viewport reference from BlockBox
* Viewport -> LayoutState (call it what it really is)
* move more stuff from box -> engine
|
|
|
|
|
| |
Viewport at this point is basically just the layout state, so it
makes no sense to store it in buffer.
|
| |
|
| |
|
|
|
|
| |
bugfix, bugfix...
|
| |
|
| |
|
|
|
|
|
|
| |
* rename module (window -> winattrs, to avoid conflict with env/window)
* do not use result
* remove unused cell_ratio
|
| |
|
|
|
|
| |
Makes LineBox objects a bit smaller.
|
| |
|
|
|
|
|
| |
Most InlineContext members may be discarded after layout, and thus
belong in InlineState.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Say we have a table
<TABLE>
<TR>
<TD WIDTH=20>a</TD>
</TR>
<TR>
<TD>aklsdfjaskdfjkl</TD>
</TR>
</TABLE>
This should be 20 pixels wide, not as wide as the second row.
Also, larger specified widths now always override previous widths
specified on the column. (I think this was a regression, but the
previous solution to this problem was an ugly hack.)
|
|
|
|
|
|
|
|
|
|
| |
* ips -> io/
* loader related stuff -> loader/
* tempfile -> extern/
* buffer, forkserver -> server/
* lineedit, window -> display/
* cell -> types/
* opt -> types/
|
|
|
|
|
| |
Now cells with a rowspan > 1 actually occupy several rows.
The implementation is quite ugly but it should work for now.
|
|
|
|
|
| |
Turns out we had the row groups separated for a reason: we need them
so we can implicitly sort rows based on their row group type.
|
|
|
|
| |
the iterator here was rather pointless
|
|
|
|
|
|
| |
Specifically, we used to set the width computed value of table cells
manually in the past. It was a hack that never worked very well, and has
been unnecessary ever since we switched to SizeConstraints.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Re-consideration of 1e0506adb: we do need to explicitly specify padding
after all, so the rendering engine knows of it too.
|
|
|
|
|
|
| |
In the tab width case, only whitespacenum was being divided instead of
charwidth + whitespacenum, which resulted in an exponential growth of
both charwidth and whitespacenum.
|
|
|
|
|
| |
So e.g. padding: 1px does not inhibit automatic addition of spaces
for inline blocks.
|
| |
|
|
|
|
| |
Still not perfect, but at least not completely broken.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
computeShift now checks if the last inline atom is spacing, and
if yes, it does not add more spacing.
This fixes rendering of the following document:
<span>
a
</span>
<span>
b
</span>
|
| |
|
|
|
|
|
| |
Only inherit width from the last positioned element if position:
absolute is set.
|
|
|
|
|
|
| |
Factor out the "shrink" variable and the (broken) isWidthSpecified into a
SizeConstraint type.
This should make box sizing easier to reason about.
|
|
|
|
| |
whoops
|
|
|
|
|
|
|
|
| |
* Set contentWidthInfinite to false when specified width commands so
* Unify applyWidth of block boxes. probably still incorrect, just less so
(at least we no longer have two slightly different cases...)
This appears to fix some infinite table cell width issues.
|
|
|
|
| |
Split it into smaller functions.
|
|
|
|
| |
urls can get pretty long
|
| |
|
|
|
|
| |
Reduces ugly rendering caused by rounding errors.
|
| |
|
|
|
|
|
| |
In other words, if the element is wider than it's container, we
don't do anything at all.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Fix margin-top being used instead of margin-bottom.
Content width resolving makes somewhat more sense now.
min-width, max-width doesn't completely break width calculation anymore.
Finally, position: absolute is no longer implemented as a horribly
broken hack.
|
|
|
|
| |
It was being used the same way as max-width. Oops.
|