about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* layout: remove obsolete todobptato2025-05-171-1/+0
|
* config: fix prepend-https parsingbptato2025-05-131-0/+1
|
* config: print warning for prepend-httpsbptato2025-05-132-2/+15
| | | | Use prepend-scheme = '' instead.
* config: remove excessive dot from warning messagebptato2025-05-131-3/+2
|
* Eliminate some superfluous copiesbptato2025-05-1117-48/+53
|
* twtstr: re-validate UTF-8 in nextUTF8bptato2025-05-111-36/+40
| | | | | it isn't used on invalid UTF-8, but the validation logic is separate so it seems better to double-check
* config: warn on unused valuesbptato2025-05-112-35/+31
|
* fromjs: switch back res to `var' from `out'bptato2025-05-105-13/+10
| | | | | | | | The original goal was to comply the Uninit warning, but this is now a futile effort as Uninit is no longer planned to be the default in Nim. Setting `res' to its type's default value is therefore just a waste of cycles when it's already zero-initialized.
* Enable ProveInit warningbptato2025-05-1012-17/+56
| | | | It has caught some minor bugs.
* config: add external.show-download-panelbptato2025-05-092-3/+4
|
* config: remove sockdirbptato2025-05-081-1/+0
|
* pager: remove pointless clampbptato2025-05-081-2/+1
|
* buffer: remove gpstream & SIGTERM handlerbptato2025-05-082-13/+1
| | | | | SIGTERM will kill us anyway, and then the control stream gets automatically closed. Fin.
* term: remove sixelMaxWidth, sixelMaxHeightbptato2025-05-072-50/+7
| | | | | | We weren't compensating for it at all, so it's kind of pointless. (AFAIK it only ever differs from the window size on XTerm, where you can just set maxGraphicSize anyway.)
* event: optimize dispatchbptato2025-05-071-40/+63
|
* event: fix another stopPropagation bugbptato2025-05-051-8/+9
|
* event: fix stopPropagation in capturing phasebptato2025-05-051-9/+11
|
* event: implement capturing phase, misc improvementsbptato2025-05-054-40/+86
| | | | Fixes acid3 tests 31, 32
* layout, csstree: build stacking contexts together with treebptato2025-05-035-69/+133
| | | | | | | | We often redo sub-layouts in layout, and this makes stacking contexts very hard to build reliably there. This fixes a bug where positioned descendants of flex items would sometimes mysteriously disappear.
* dom, event: add UIEvent to createEvent, initUIEventbptato2025-05-033-7/+41
| | | | Fixes acid3 test 30
* term: do not accept BEL in query responsesbptato2025-05-031-5/+5
| | | | We no longer send it, so terminals shouldn't send it either.
* url: add schemeType, fix port bug on protocol assignmentbptato2025-05-038-120/+152
| | | | Allows branching on the scheme without string comparisons.
* url: simplify tuple originbptato2025-05-031-33/+8
|
* pager: do not forget downloads buffer on replacebptato2025-05-021-0/+2
|
* cookie: do not match port in Domainbptato2025-05-021-7/+7
| | | | That's how cookies *should have* worked, not how they actually work.
* container: optimize object sizebptato2025-05-022-19/+17
|
* container: support Refresh headerbptato2025-05-023-47/+63
|
* url, twtstr: misc cleanup, fix overflow check in parseUInt8bptato2025-05-012-112/+86
|
* myaddr: fix newSeqUninit polyfillbptato2025-05-011-1/+1
| | | | | | Sometimes it's called with an unsigned len. ref. https://todo.sr.ht/~bptato/chawan/59
* history: simplify a bitbptato2025-04-302-22/+13
|
* myaddr: backport & switch to newSeqUninitbptato2025-04-307-17/+22
|
* config: misc optimizationbptato2025-04-291-4/+4
|
* config: fix arrays not being cleared on reassignmentbptato2025-04-291-0/+1
|
* term: support vt52bptato2025-04-281-6/+13
|
* term: reduce Termdesc sizebptato2025-04-271-43/+42
| | | | now it fits into 1 byte
* term: misc fixes, support rxvtbptato2025-04-251-42/+49
|
* term: misc fixes, support adm3abptato2025-04-241-55/+93
|
* term: replace termcap with a built-in terminal databasebptato2025-04-233-186/+161
| | | | | | | | | | | | | I considered using terminfo, but it works *worse* on several terminals I've tried than whatever this is. So out with ncurses, I say. In this new scheme, if the terminal is unrecognized, it is assumed to be XTerm-compatible. This does mean that an unrecognized terminal that doesn't do XTGETTCAP or COLORTERM will not get true colors. Another drawback is that non-VT-compatible terminals now have zero chance of working. This is unfortunate, but realistically they probably didn't work until now either.
* layout: simplify resolveBoundsbptato2025-04-231-31/+19
| | | | | Not entirely sure what the px check for the mi[dtHorizontal].send assingment was for; tests still pass after removing it.
* cssparser: optimize CSSToken sizebptato2025-04-181-2/+2
| | | | 4 -> 3 words
* selectorparser: check type flag of hash tokensbptato2025-04-182-10/+6
|
* toml: fix underscores in integer literalsbptato2025-04-171-9/+8
| | | | while at it, prefer seek to discarding consume
* config: remove bindPagerKey, bindLineKeybptato2025-04-171-6/+0
| | | | undocumented and likely unused.
* loader: remove obsolete commentbptato2025-04-171-1/+0
|
* pager: remove obsolete acceptBuffersbptato2025-04-171-28/+14
| | | | Hopefully this didn't break anything...
* loader: use pipes in network streamsbptato2025-04-172-13/+11
| | | | | | | | | | | Turns out we don't actually have a reliable mechanism to detect broken streams - if a pipe is broken, well, it's broken, but that's about all we know. It seems UNIX sockets didn't trigger the code path, but pipes do now, and it was causing issues (reporting some correctly ended streams as broken). This is not fixable with the current protocol, so for now, I've just made onError do the same as onRead at EOF.
* main: ensure that we own tmpdirbptato2025-04-171-9/+14
| | | | | | | | Otherwise a malicious user on the same machine could get access to the directory. (This isn't problematic in theory, since such users still wouldn't have access to the temp files. Still, better safe than sorry.)
* pager: remove unused fieldbptato2025-04-171-7/+6
|
* loaderiface: return PosixStream for startRequestbptato2025-04-154-11/+10
|
* toml: remove broken special case, update docsbptato2025-04-151-10/+2
| | | | | | Turns out the cure was worse than the disease. Let's just make it a backwards incompatible change, so that at least the error message is no longer nonsensical.