| Age | Commit message (Collapse) | Author |
|---|
|
Adding the extra flags to search Mbed TLS in CFLAGS and LDFLAGS directly
inhibits AC_PROG_CC from injecting the usual -O2 and -g flags. Instead,
we add them to MBEDTLS_* set of variables which are only used to locate
Mbed TLS. Then we pass them to the Makefile via AC_SUBSTAC_SUBST().
We also move the LIBSSL_* flags to be early on the order of dillo_LDADD,
so that extra -L flags which can be injected from fltk-config or other
programs, don't accidentally point to /usr/lib or a similar location
where it could race with another installation of Mbed TLS.
This mechanism won't work for cases in which Mbed TLS has libraries
installed in a location other than the default search path, but works
for Arch Linux and Gentoo because the symlink them to the default search
path, even if they are installed in a different location.
|
|
Implements support for brotli (br) content encoding.
Fixes: https://github.com/dillo-browser/dillo/issues/377
|
|
|
|
Allows the user to define additional entries in the link menu which will
execute the given program/script. Each actions is defined using the
"link_action" option. The link URL is stored in the $url enviroment
variable and the current page in $origin, so the user can customize how
do the handling.
Here is a simple example to add three new entries:
link_action="Debug variables:echo url=$url origin=$origin"
link_action="Open in MPV:mpv $url"
link_action="Open in Firefox:firefox $url"
The command is spawned in a forked process using the system() call,
which uses the shell to expand any variable. In particular, the $url
variable is set to the current URL being opened.
Fixes: https://github.com/dillo-browser/dillo/issues/3
|
|
Add the target commit.h as a dependency of version.o, so it gets
generated before being included in version.cc, otherwise when doing a
parallel build it can fail.
|
|
Compare the commit used in the last rebuild to determine if it has
changed, rather than using a phony target which always causes a rebuild.
|
|
When git is available, records the git commit in the dillo binary, so
dillo -v reports the version and the commit. Otherwise only the release
version is reported (as we do now).
The commit is *always* recomputed when "make" is called. This allows
switching branches, doing a dirty rebuild and still get the correct
commit with "dillo -v".
Using AC_INIT() doesn't update the commit when the source is already
configured.
Fixes: https://github.com/dillo-browser/dillo/issues/288
|
|
See: https://www.toomanyatoms.com/software/mobilized_dillo.html
Authored-By: dogma
|
|
When reporting the version of Dillo with -v, print also the version of
the libraries it is currently using, as well as the features that were
enabled at build time. Notice the versions are reported by reading them
at runtime, so we can detect the version loaded at run time, regardless
of which version was used at link time.
All features are always printed, but prefixes with + if enabled or - if
disabled. This allows checking if the feature was disabled at configure
time or if it is missing in that version of Dillo.
|
|
Uses the nanosvg library to add SVG support.
See: https://www.toomanyatoms.com/software/mobilized_dillo.html
Authored-By: dogma
|
|
|
|
|
|
I'm not including the preload file yet.
|
|
Normally I really like to make commits in small pieces that all compile
and make sense in isolation, but with this https work, the effort vs the
reward just wasn't going to make sense.
|
|
|
|
some of them are more than one unicode codepoint. I know there were cases
that resulted in six bytes, which could in principle be longer than the
reference that it's replacing (e.g., "&" is five bytes). So this
required some reworking.
As for (mostly) duplicating the strings for html4 and html5, ⟨ and
⟩ are currently different and it would have felt a little silly in
2014 to have, say, a bool for whether an html5 ref appears in html4 plus
special code for lang/rang.
|
|
|
|
does not seem to work).
|
|
Removed the workaround [1] that added a full UI and viewport
redraw to conceal the lingering tooltips bug [2]. It produced
annoying scroll flickering when the mouse was in the UI but
outside the viewport (e.g. over the panel).
This is more a FLTK bug than anything; the FLTK team's plan is
to fix it in FLTK3, and also extend the tooltips API.
As FLTK3 may take long to be released, and porting dillo to it
is non-trivial (if both events ever come to happen), this custom
solution looks quite reasonable for the present times.
The patch introduces a new CustButton class that uses TipWin,
and thus the tooltip handling is no longer handled by FLTK. This
patch switches the UI buttons to the new CustButton.
1] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-July/008515.html
2] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-July/008494.html
|
|
|
|
|
|
Justus contributed the original patch in April 2009.
I read RFCs, fixed bugs, restructured, tested.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The --xid option is used by a plugin for the claws mail client
(http://www.claws-mail.org/) to embed the dillo window into the mailer
application to display HTML mails.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Set some new default values in prefs.
|
|
|
|
|
