Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
Reviewed-by: Rodrigo Arias Mallo <rodarima@gmail.com>
See: https://lists.mailman3.com/hyperkitty/list/dillo-dev@mailman3.com/thread/XXD2NXCGQLZLJ3V57NCPU3327DAEFKAN/
|
|
Small laptops and netbooks that lack a proper 3 button touchpad make it
difficult to open a new tab. Using the control modifier makes is easier
to open links in new tabs. It also allows mixing it with the shift
modifier to control the focus.
|
|
Fixes: https://github.com/dillo-browser/dillo/issues/66
|
|
It is deprecated and got removed.
See: https://github.com/actions/runner-images/issues/11101
|
|
Implements support for brotli (br) content encoding.
Fixes: https://github.com/dillo-browser/dillo/issues/377
|
|
See: https://github.com/dillo-browser/dillo/actions/runs/14285249224/job/40039689315#step:3:136
|
|
|
|
Allows inspecting their content before adding it to a feed reader by
reading it as plain text.
|
|
The .deps folders are part of the build process and dirty git status.
This ignores them in the project.
|
|
When the page is first layouted, we can then determine if the vertical
scrollbar needs to be present. When the vertical scrollbar is on the
left side, the whole content needs to be shifted to the right, so we
need to allocate the top level widget again. The current fix simply
marks the top level widget for allocation.
Fixes: https://github.com/dillo-browser/dillo/issues/359
|
|
Ensure that we don't accidentally add newer features by building with
-std=c++11 only on the CI build.
|
|
Remove extra semicolons and commas, as well as isinf() so it builds and
runs on Solaris 10.
Also add extra fixes for non C++11 courtesy of Sevan Janiyan, making
Dillo compile and run on OS X 10.4 PowerPC with GCC 4.0.1 and 8.5.
Co-authored-by: Sevan Janiyan <venture37@geeklan.co.uk>
|
|
Don't force full C++11 support, as we only require a very small subset
of features that may be available in the compiler as extensions like
GNU.
|
|
See: https://lists.mailman3.com/hyperkitty/list/dillo-dev@mailman3.com/thread/L3FFAINJJMIOZQNID5HC2DHKJIIIHEYH/
|
|
Since 3.2.0 the new tab is no longer automatically focused by default.
|
|
nsvg__isspace uses strchr on a NUL terminated string, so it returns
true for the NUL terminator. Other uses of nsvg__isspace account for
this by checking for NUL first; I've followed the same pattern here.
Fixes: https://github.com/memononen/nanosvg/issues/241
See: https://github.com/memononen/nanosvg/pull/262
|
|
See: https://github.com/memononen/nanosvg/pull/252
|
|
|
|
|
|
|
|
On cases where the system directory cannot be opened, dpid will not load
the builtin plugins causing Dillo to fail to work properly with file: or
data: URLs. Reporting a failure to open the directory allows users to
determine the cause of the problem.
See: https://github.com/dillo-browser/dillo/issues/337
|
|
|
|
|
|
Line numbers can be referenced using the fragment L + line number. For
example, file://foo/bar.txt#L42 will cause Dillo to scroll to line 42.
Fixes: https://github.com/dillo-browser/dillo/issues/330
|
|
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.
|
|
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/
|
|
The returned value from Fl::version() is a floating point number like
1.0303, not 10303, so we correct it to follow Fl::api_version().
|
|
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
|
|
The Fl:api_version() method is not available on FLTK 1.3.3 and older, it
needs to use Fl::version() instead.
|
|
Makes disabling certain formats posible without the need to rebuild
Dillo from source.
See: https://github.com/dillo-browser/dillo/pull/312
|
|
Limit the push events to the master branch, otherwise they will be
running twice on every feature branch and PR.
|
|
Homebrew has updated the default version of FLTK to 1.4, which is
causing rendering issues in Dillo. So for now, we build with FLTK 1.3 by
pinning it.
See: https://github.com/Homebrew/homebrew-core/pull/198029
See: https://github.com/dillo-browser/dillo/issues/246
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
There are several problems that need to be resolved before we can switch
to FLTK 1.4. The support is intentionally disabled until it is ready.
See: https://github.com/dillo-browser/dillo/issues/246
|
|
Following https://datatracker.ietf.org/doc/html/rfc7230#section-5.3.1,
the path must not be empty, even if we have a query:
> If the target URI's path component is empty, the client MUST send "/"
> as the path within the origin-form of request-target.
Notice URIs can have empty paths, this is a restriction of HTTP only.
Fixes: https://github.com/dillo-browser/dillo/issues/302
|