| Age | Commit message (Collapse) | Author |
|---|
|
See: https://lists.mailman3.com/hyperkitty/list/dillo-dev@mailman3.com/thread/L3FFAINJJMIOZQNID5HC2DHKJIIIHEYH/
|
|
Send the user agent to the downloads DPI so we can use the same as
Dillo uses from the http_user_agent option.
See: https://lists.mailman3.com/hyperkitty/list/dillo-dev@mailman3.com/thread/A6IHJ4TBGHJ3CT2UOMEAROSG2WRTRO6U/
|
|
Reviewed-by: dogma
|
|
Reviewed-by: dogma
|
|
Uses the nanosvg library to add SVG support.
See: https://www.toomanyatoms.com/software/mobilized_dillo.html
Authored-By: dogma
|
|
Make the background of line numbers appear as a single color and
increase the contrast to improve readability. Also add a bit of
space and a separator line between the numbers and the code itself.
|
|
They allow linking to an specific line in the source code. This would be
useful to add to the bug meter view, so the user can quickly jump to the
error line in the HTML source.
Fixes: https://github.com/dillo-browser/dillo/issues/214
|
|
The destructor was using a harcoded index to the elements to free from
the original array of arguments used to call the wget program. When the
user agent was introduced, the index of the elements that require free()
shifted, causing the free() call to operate on the constant string of
the user agent instead.
Rather than relying on the hardcoded index, two new pointers hold the
values of the strings that need to be free()'d in the destructor.
Further additions in the argument array won't cause more problems.
Reported-by: pastebin <pastebin@gmx.com>
Fixes: https://github.com/dillo-browser/dillo/issues/196
See: https://lists.mailman3.com/hyperkitty/list/dillo-dev@mailman3.com/message/IPWQYKTYTO5G2BH3UU5224FRUFWCVGSO/
|
|
The file plugin was not able to detect XHTML documents from files with
the .xhtml extension if there are comments before the doctype line.
Before falling back to reading the content, we directly specify the
media type to HTML based on the extension alone.
The basic content type detection algorithm is too simple and will
continue to fail when comments are placed before the doctype line.
Reported-by: Kevin Koster <dillo@ombertech.com>
See: https://lists.mailman3.com/hyperkitty/list/dillo-dev@mailman3.com/message/HBKXGO7EGCHWOQ6BM55A4LZQKT437UID/
|
|
Reported-by: dogma
|
|
Fixes: https://github.com/dillo-browser/dillo/issues/130
|
|
|
|
Reported-by: dogma
Fixes: https://github.com/dillo-browser/dillo/issues/112
|
|
Simplifies and increases the contrast of the Bookmark pages and menus.
Tables are removed in favor of HTML5 elements. For styles we add a
simple CSS style sheet, common for all pages.
Fixes: https://github.com/dillo-browser/dillo/issues/108
|
|
Reported-by: dogma
|
|
Other platforms don't use $HOME.
Reported-by: dogma
|
|
Fixes: https://github.com/dillo-browser/dillo/issues/87
Reported-by: dogma
|
|
Allows paths like "file:~/" and "file:~/.dillo/dillorc" to be opened by
Dillo by expanding the tilde character '~' to the value of the $HOME
environment variable.
Fixes: https://github.com/dillo-browser/dillo/issues/81
|
|
Fixes #1 by setting the user agent to "Dillo/3.0.5".
A proper fix must let the user choose any string.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
...not that there's any obvious justification for storing cookies for decades.
|
|
FWIW, wget currently does it as follows:
"If you modify this program, or any covered work, by linking or
combining it with the OpenSSL project's OpenSSL library (or a
modified version of that library), containing parts covered by the
terms of the OpenSSL or SSLeay licenses, the Free Software Foundation
grants you additional permission to convey the resulting work.
Corresponding Source for a non-source form of such a combination
shall include the source code for the parts of OpenSSL used as well
as that of the covered work."
|
|
|
|
BTW, is there a point in using a monospaced font?
Besides it looks like code printing (which is good),
a proportional-spaced font may be easier to read.
|
|
Although not allowed in text contexts, null characters should not
stop/halt/fail dpi protocol, thus the patch.
Test Example. Display a file with these contents:
null padding^@^@
(two trailing null characters)
and view source for it.
Note that dillo will not _display_ the file completely correct,
it will eat a char after each null, but this is not a problem in
dpi nor dpip but in rendering, the cache gets it right.
Adding code to correctly _display_ these anomalous pages is probably
not worth the effort though.
|
|
|
|
in January 2010, there were 42 entries. Now there are 22, and nearly all of
them are rather...marginal.
|
|
|
|
|
|
|
|
|
|
in January 2010, there were 42 entries. Now there are 22, and nearly all of
them are rather...marginal.
|
|
|
|
BTW, is there a point in using a monospaced font?
Besides it looks like code printing (which is good),
a proportional-spaced font may be easier to read.
|
|
Although not allowed in text contexts, null characters should not
stop/halt/fail dpi protocol, thus the patch.
Test Example. Display a file with these contents:
null padding^@^@
(two trailing null characters)
and view source for it.
Note that dillo will not _display_ the file completely correct,
it will eat a char after each null, but this is not a problem in
dpi nor dpip but in rendering, the cache gets it right.
Adding code to correctly _display_ these anomalous pages is probably
not worth the effort though.
|
|
|
|
|
|
|
|
|
|
SSLv2 is considered insecure.
submitted by: p37sitdu@lavabit.com
|
|
|
|
|
|
|
|
Bug fix: also avoid a useless retry when given just the server name.
|
