| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |
|
|
|
|
| |
* simplify processData
* set document charset on creation
* update chagashi
|
| | |
|
| |
|
|
| |
this one is weird but I'm sure the standard is technically right
|
| |
|
|
|
|
|
|
| |
ok we block if:
* method is not GET
* scheme is different
* it is not the case that both the current and the target schemes are
http/s
|
| |
|
|
| |
bleh
|
| |
|
|
| |
the Option setup hasn't made much sense for a long time now
|
| | |
|
| |
|
|
| |
naturally, it's opt-in
|
| |
|
|
|
|
| |
* refactor form submission
* add options to specify form handling per protocol
* block cross-protocol POST requests
|
| | |
|
| |
|
|
|
|
| |
Not very useful yet; partial layouting and/or a new renderer is probably
necessary to replace the current FormatCell-based node placement,
otherwise it will be unbearably slow.
|
| |
|
|
| |
Operation "modularize Chawan somewhat" part 3
|
| |
|
|
|
|
|
| |
It's easier to just use nested seqs here.
(This also fixes reverse-search highlighting the last capture group
instead of the whole match.)
|
| |
|
|
|
|
| |
Interface:function -> Interface.function
for consistency with regular JS syntax
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a minefield.
Intuitively, you would think that just clearing the opaque and manually
freeing registered object should be enough. Unfortunately, this is
not true; we do not store whether we are actually holding a reference to
registered JS objects, so this approach leads to double frees.
Instead, we add a QJS callback that is called right after the final
GC cleanup, but before the list_free assertion. This way, we can be sure
that any object still in our registry is referenced by us, and can
therefore unreference them safely.
|
| |
|
|
| |
just sync'ing
|
| |
|
|
| |
Parse rule values in sheet addRule, not during cascade.
|
| |
|
|
|
| |
See attached test case; previously, this would result in a missing space
in visual mode and a crash in dump mode.
|
| |
|
|
|
| |
* get rid of BlockGroup
* unify BlockBox construction for flex, block, table
|
| |
|
|
|
|
|
| |
Much cleaner than the previous solution.
Should also be somewhat less wasteful, as we no longer constantly
rebuild the same tree with new branches.
|
| | |
|
| |
|
|
| |
get rid of percHeight, unify min/max sizing, etc.
|
| | |
|
| | |
|
| |
|
|
|
| |
* do not use inline block computed values for wrapper fragment
* fix minimum line box height calculation
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous solution had the issue that it switched between "delete
buffer, then move back" and "delete buffer, then move forward" depending
on whether the buffer was the root of the buffer tree, which made its
behavior quite unpredictable.
Now the pager (sort of) remembers the direction you are coming from,
and D moves in that direction. So e.g.:
* Enter, D just moves back to where you were coming from (as before)
* Comma, D deletes the previous buffer, then returns to the current
buffer
If no buffer exists in the target direction, then we alert.
Also, new commands are: `d,' `d.'. They do the same thing the
non-d-prefixed variations do, but also delete the current buffer. Useful
if you're no longer sure where you are coming from, but know where you
want to go. (`d,' in particular is equivalent to w3m's `B'.)
|
| |
|
|
|
|
|
| |
As expected, the mystery line was just hiding another bug. (In
particular, indefinite containing size constraints were not denied in
resolveContentWidth, so it only (accidentally) worked with stretched
sizes.)
|
| |
|
|
| |
seems like this line is necessary after all
|
| | |
|
| |
|
|
|
|
| |
* merge caption sizing code path with layoutRootBlock
* fix caption margins being disregarded
* fix incorrect positioning of `caption-side: bottom'
|
| |
|
|
|
| |
* use current fragment's line height for percentage baselines
* get rid of baseline calculating pass in verticalAlignLine
|
| |
|
|
|
|
|
|
| |
TODO: find the exact flags we need instead of -fpermissive.
See also:
https://todo.sr.ht/~bptato/chawan/12
https://forum.nim-lang.org/t/11587
|
| |
|
|
|
|
|
|
|
|
|
| |
As per standard:
> Adjoining vertical margins collapse, except:
> [...]
> If the top and bottom margins of an element with clearance are
> adjoining, its margins collapse with the adjoining margins of
> following siblings but that resulting margin does not collapse with
> the bottom margin of the parent block.
|
| | |
|
| |
|
|
| |
just merge it with InlineFragment
|
| | |
|
| | |
|
| |
|
|
| |
This avoids some unnecessary string copying.
|
| |
|
|
| |
this way, we do not refer to nodes of previous cascade passes
|
| |
|
|
|
|
|
|
|
|
| |
Instead of allocating a separate object for each box, just re-use
a single BlockBox on re-layouts.
This means that now the (block-level) tree is built in its final form in
the first pass.
(Inline boxes remain the same as before for now.)
|
| |
|
|
|
| |
* fix list-style-position: inside
* get rid of ListItemBoxBuilder
|
| |
|
|
|
|
|
|
|
| |
Captions are no longer positioned inside tables, yay.
Also, misc:
* rename some things for consistency
* clamp out of bounds rgb() values
* remove inherited property lookup table
|
| |
|
|
|
| |
This is not a perfect solution, but it's still better than not being
able to double click on CJK links correctly.
|
| |
|
|
|
|
|
| |
Pointless bloat that fixes no real problems, but it's standard now...
(Are we supposed to add a helper function that returns null for *every*
constructor that can throw now?)
|
| |
|
|
|
| |
I wish we didn't need any, but fixing this for integers would be too
involved and the float64 one was causing problems now.
|
| |
|
|
| |
removes elaborate table box type hierarchy that does nothing
|
| | |
|
| |
|
|
| |
seems to get called for signal handlers
|
| |
|
|
| |
rationale: see previous commit
|