Age | Commit message (Collapse) | Author |
|
|
|
The libpng library may emit warnings when decoding a PNG image, which
are non-fatal. So far we were handling them as errors and stopping the
decoding process, which prevents Dillo from decoding some images. In
particular, images that emit the warning:
> iCCP: known incorrect sRGB profile
Fixes: https://github.com/dillo-browser/dillo/issues/179
Authored-by: dogma
|
|
It may be returned when the server closes the connection, see:
https://www.openssl.org/docs/manmaster/man3/SSL_get_error.html
We simply handle it as if there was no error and return zero bytes read.
Fixes: https://github.com/dillo-browser/dillo/issues/175
|
|
|
|
Cygwin doesn't seem to support detached threads used by the threaded DNS
resolver at the same time the dynamic OpenSSL library is used. As a
workaround we suggest disabling the threaded DNS (will use the same
thread) if building with OpenSSL on Cygwin.
Fixes: https://github.com/dillo-browser/dillo/issues/172
|
|
In Mbed TLS 3.6.0 there is support for TLSv1.3 but it requires
special handling, so for now we disable it.
See: https://gitlab.alpinelinux.org/alpine/aports/-/commit/4dc36afaa81a4d73758b29fa77981d07dbae0080.patch
Fixes: https://github.com/dillo-browser/dillo/issues/158
|
|
Fixes: https://github.com/dillo-browser/dillo/issues/160
|
|
|
|
Implement an option to force all http urls to be upgraded to HTTPS,
similar to HTTPS-Only Mode in Firefox.
A http_force_https preference variable is provided as well as a menu
bar item to toggle this mode.
See: https://support.mozilla.org/en-US/kb/https-only-prefs
|
|
Partially reverts commit f5a0b6030c2001e5a0fcacf8139afa800643eb47.
Fixes the rendering test table-missing-width-in-one-column.
Fixes: https://lists.mailman3.com/hyperkitty/list/dillo-dev@mailman3.com/message/H7JEBC2HYNJ6FUPQM7ILBP7I5FLU33IZ/
|
|
Fixes: https://github.com/dillo-browser/dillo/issues/136
|
|
Fixes: https://github.com/dillo-browser/dillo/issues/141
|
|
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/
|
|
A lot of sections were updated and extended to cover the usage of the
browser from the perspective of a new user. Other missing content was
added, specially to describe the configuration files and the format they
use.
Fixes: https://github.com/dillo-browser/dillo/issues/73
|
|
|
|
The W3C validator is now protected under a CloudFlare JavaScript
challenge. However, it can be bypassed by opening directly the link
after the redirection. It doesn't work if an HTML 5 page is loaded, as
that would redirect to the Nu validator which will attempt to run the
challenge again.
So the current solution is to use the "legacy" W3C validator for HTML
4.01 or older documents and the W3C Nu validator for HTML 5 documents
only. Users would need to choose which one to use manually (at least for
now).
The WDG validator at https://www.htmlhelp.org/tools/validator/ is gone,
the server reports "Server unable to read htaccess file, denying access
to be safe", so it has been removed.
Fixes: https://github.com/dillo-browser/dillo/issues/113
|
|
Fixes: https://github.com/dillo-browser/dillo/issues/109
|
|
On Cygwin the binaries have the ".exe" extension, so the logic to detect
dpi files has to take it into account when scanning the dpi_dir. The
extension DPI_EXT is defined to ".dpi" or ".dpi.exe" depending on the
platform extension discovered by autoconf.
Similarly, the dpidrc configuration file is also configured to match the
name of the DPI binaries.
See: https://github.com/cygwinports-extras/dillo/blob/master/3.0.2-exeext.patch
Fixes: https://github.com/dillo-browser/dillo/issues/105
|
|
|
|
The width attribute in tr and td tags is deprecated in HTML 4.01 and
obsolete in HTML 5. However, we should still support it when loading the
page in the transitional mode.
Currently, the relative values of the width attribute are transformed
into CSS values. They cause the available text width to be computed by
applying the relative value to the cell width, which causes an
unintended effect.
The workaround for now is to simply ignore the value when it is
specified as a percent.
|
|
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
|
|
We cannot rely on the return value and the errno, the function
SSL_get_error() must be used to determine what happen and if we need to
retry again. A wrapper function translates the SSL error into a proper
errno value.
In the case a premature EOF is sent by the server, the error queue is
emptied before the error is returned.
Fixes: https://github.com/dillo-browser/dillo/issues/79
|
|
|
|
The default tab height of 16 pixels was causing some usability issues as
the tabs are quite small in large monitors. The default size is
increased to 20 pixels and the new option "ui_tab_height" allows the
user to specify a different value.
|
|
The website is now at https://dillo-browser.github.io/ and the
repository at https://github.com/dillo-browser/dillo.
|
|
|
|
These tests render a HTML page in Dillo and save a screenshot which is
compared with another one rendered by a reference HTML file which
doesn't make use of the feature under test.
Running these tests require some additional dependencies to run a Xorg
server and capture screenshots of the browser, so they are only enabled
when configured with the --enable-html-tests option.
Additionally, running Dillo and opening local files requires a working
file dpi plugin. So, when running the HTML tests it is required that a
working dpid server can be launched by Dillo. To do so, Dillo can be
first installed to a prefix directory, the dpidrc file copied to
~/.dillo/ and then the DILLOBIN variable set to the path of the dillo
binary under test.
|
|
|
|
|
|
When using the mouse wheel to scroll a page, the default scroll step was
causing a very slow scrolling speed. The new option "scroll_step" allows
the user to define how many pixels the page is moved in every step of
the mouse wheel. The default is increased to 100 pixels per step.
|
|
The DuckDuckGo service that redirects the links from the search page is
returning a broken page for non-javascript browsers. They have a meta
refresh tag in the body, instead of in the head.
Adding the kd=-1 argument causes the DuckDuckGo search results to point
directly to the target page avoiding the redirection.
Based on this patch:
https://salsa.debian.org/debian/dillo/-/commit/ffbd4fc0e6cf94b3947d02766224c0e80344a017
Thanks: liftof+dbug@gmail.com
Thanks: Axel Beckert <abe@debian.org>
Bug-Debian: https://bugs.debian/org/924357
|
|
|
|
|
|
z-index, stacking contexts) have been removed and will be added when they are completely implemented.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
looks like we lost it in
"changeset 2768:e7f98f931ed7
Modified a_Dialog_choice5() to accept any number of alternatives [p37sitdu]"
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|