| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
This fixes a bug where setContentType would call setHTML twice, which
messed up charsets and probably a couple more things. As a bonus, it
allows us to pass around the content type less.
In fact, buffer does not have to know its exact content type, just
whether it is in HTML mode or not. So that's all we tell it now;
only container still keeps track of the content type (as it should).
|
|
|
|
|
|
| |
default-flags was overly complicated for its purpose.
Also, ignore-case is quite useful, so enable it by default.
|
|
|
|
|
|
| |
The API is horrid :( but at least it copies less.
TODO: think of a better API.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The way `justify' was implemented just made text annoying to read.
(The algorithm of distributing spacing evenly does not really work
on a cell-based screen because of rounding errors.)
CSS 2.1 says:
> Conforming user agents may interpret the value 'justify' as 'left' or
> 'right', depending on whether the element's default writing direction
> is left-to-right or right-to-left, respectively.
Since we have no bidi yet, just interpret it as `left'.
Maybe in the future we could add an implementation that tries to align
line box lengths instead of their contents, but this will probably be
difficult to get right.
|
|
|
|
|
|
| |
The first line is already ignored in the calculations, but it was still
being re-positioned in positionAtoms, which made lines overlap in some
cases.
|
| |
|
|
|
|
|
| |
* set loaderPid in clones too
* handle URL in container the same way as in buffer
|
|
|
|
|
| |
source.request.url is not used after buffer initialization (because it
may be replaced later), so we must set buffer.url instead.
|
|
|
|
|
| |
* do not eat \\c, \\C
* emulate vi-style word boundary matching (\<, \>) with \b
|
|
|
|
| |
We have less than 8 flags, so the set's size is 1.
|
| |
|
| |
|
|
|
|
|
|
|
| |
I've gotten tired of not being able to search for forward slashes.
Now it works like in vim, and you can also set default ignore case in
the config.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Until now, the config file required manual adjustment for the output to
look bearable on terminals colored differently than {bgcolor: black,
fgcolor: white}. Also, it only detected RGB when COLORTERM was set, but
this is not done by most (any?) terminal emulators (sad).
To improve upon the situation, we now query the terminal for some
attributes on startup:
* OSC(10/11, ?) -> get the terminal's bg/fgcolor
* DCS(+, q, 524742) -> XTGETTCAP for the "RGB" capability (only
supported by a few terminals, but better than nothing)
* Primary device attributes -> check if ANSI colors are supported, also
make sure we don't block indefinitely even if the previous queries
fail
If primary device attributes does not return anything, we hang until
the user types something, then notify the user that something went
wrong, and tell them how to fix it. Seems like an OK fallback.
(The DA1 idea comes from notcurses; since this is implemented by pretty
much every terminal emulator, we don't have to rely on slow timing hacks
to skip non-supported queries.)
|
|
|
|
| |
no need for every new buffer to query the window size
|
|
|
|
|
|
|
| |
The `t' field was completely redundant, as it's already included in the
CSSComputedValues index.
+ removed some unused functions
|
|
|
|
|
|
| |
* fix accidental dependency on previously chosen bgcolor (ouch)
* also draw empty background boxes for bgcolor-is-canvas boxes
* remove unused variable
|
|
|
|
|
|
| |
This is required by the standard. (Without this, lots of websites have
incorrect background colors, because they set the body height to 100%
of the viewport.)
|
|
|
|
|
|
|
|
| |
charwidth is specifically intended to represent the width of all
characters until the current one, so resetting it for words makes no
sense. Originally it was reset for all atoms *except* words; 9fdea97d
simplified the code incorrectly (flipped the logic) and thus introduced
a regression.
|
| |
|
|
|
|
|
| |
Without this we were wrapping on the last dash (if any) inside CJK
sentences.
|
|
|
|
| |
but I forgot to ensure the output stream gets closed. :(
|
|
|
|
|
|
|
|
| |
cha -d <some-file was crashing loader, because it was trying to register
the regular file in the selector.
this patch fixes the problem, but the control flow of loader looks like
spaghetti now
|
|
|
|
| |
otherwise pages from stdin have a race condition in dump
|
|
|
|
| |
Return the empty string if it's unset.
|
|
|
|
|
|
| |
Otherwise, container will just happily kill the buffer and with it the
loader process before it would have had the chance to stream out the
input into the external process.
|
|
|
|
|
|
|
|
| |
* disallow Stream interface usage on non-blocking PosixStreams
* do not read estream of forkserver byte-by-byte (it's slow)
* do not call writeData with a zero len in formdata
* do not quote numbers in mailcap quoteFile
* remove some unused stuff
|
| |
|
|
|
|
|
| |
readFromFd replacing the base URL of the buffer turns out to be a very
bad idea.
|
|
|
|
| |
also spawn less processes in some cases
|
|
|
|
| |
TODO should be configurable
|
| |
|
|
|
|
|
| |
Speeds up processing of pretty much all documents, because we rarely
need to switch the charset after having downloaded the first chunk.
|
| |
|
|
|
|
|
|
|
|
| |
* factor out pushBuffer to make loadFromCache async
* fix incorrect cache path
* replace rewind with loadFromCache (it does the same thing except
actually works)
* remove rewindImpl callback, rewind in buffer instead
|
| |
|
|
|
|
|
| |
do_reshape could move the target element, and thus call click on the
wrong clickable.
|
|
|
|
| |
it broke line info in console since it's never fully loaded
|
| |
|
|
|
|
|
| |
* show submission URL on hover for all form-associated elements
* skip non-checked checkbox/radio inputs
|
| |
|
| |
|
|
|
|
| |
unused (hopefully forever)
|
|
|
|
| |
useful for filtering stuff through commands like rdrview
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
At last all BufferSources are unified.
To achieve the same effect as the previous CLONE source type, we now
use the "fromcache" flag in Request. This *forces* the document to be
streamed from the disk; if the file no longer exists for some reason,
an error is returned (i.e. the document is not re-downloaded).
For a document to be cached, it has to be the main document of the
buffer (i.e. no additional resources requested with fetch()), and
also not an x-htmloutput HTML file (for those, the original source is
saved). The result is that toggleSource now always returns the actual
source for e.g. markdown files, not the HTML-transformed version.
Also, it is now possible to view the source of a document that is
still being downloaded.
buffer.sstream has almost been eliminated; it still exists, but only as
a pseudo-buffer to interface with EncoderStream and DecoderStream. It no
longer holds the entire source of a buffer at any point, and is cleared
as soon as the buffer is completely loaded.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Crucially, *only* between full-width characters.
So "あ\nあ" is rendered as "ああ", but "あ\na" remains "あ a" (with a
space inbetween).
|
| |
|