| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Whatever is searched in a incognito session shouldn't go to the
history, not even if this will be deleted afterwards.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "form-auth-data-save-requested" signal was not properly disconnected
as the g_signal_handlers_disconnect_by_func() was using the wrong
object.
The "allow-tls-certificate" signal was not disconnected at all.
The "notify::favicon" was needlessly disconnected (it will be
disconnected when the web view disappears).
And the "cleared" signal for the history service was never disconnected.
g_signal_connect_object() should ensure that all the signals we connect
to that have the web view as data are disconnected when the web view is
destroyed.
https://bugzilla.gnome.org/show_bug.cgi?id=735706
Conflicts:
embed/ephy-web-view.c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The uri-tester is created from the web extension. When created, it opens
~/.config/epiphany/adblock/filters.list for reading in
uri_tester_load_filters(), then calls uri_tester_set_filters() with the
read filters. uri_tester_set_filters() unconditionally calls
uri_tester_save_filters(), so we immediately write back what we read to
filters.list. But this is racy: if you are starting multiple web
processes at the same time, such as when opening epiphany with multiple
saved tabs, then one process may open the file for reading after another
has opened it for writing (which clears the file) but before the filters
have been written back to the file, so now one UriTester instance has an
empty list of filters, and it will immediately write back that empty list.
The original list is completely doomed because the only time we ever
write to filters.list is immediately after the filters are read, since
we do not support modifying filters. That's right, these writes are
NEVER necessary, so let's just remove them completely so we can be
completely sure the problem is gone.
Now we have an ununsued uri_tester_save_filters() function, but I don't
want to get rid of it quite yet as I do want to support at least a
couple different types of filters in the future (for tracking
protection). Also, there are already other unused functions here as
well, so one more is no difference for now, but refactor is imminent.
https://bugzilla.gnome.org/show_bug.cgi?id=697329
|
|
|
|
|
|
| |
This reverts commit a47608b090e5cd7700820dc9be0674df3c1e8644.
String freeze...
|
| |
|
|
|
|
|
|
| |
That will help debugging future issues with extensions not being found.
https://bugzilla.gnome.org/show_bug.cgi?id=727139
|
|
|
|
|
|
|
|
| |
The UI side relies on having the name of the owner to find the extension on
its linked list. If we start emiting signals before that has been acquired,
we will miss page created signals.
https://bugzilla.gnome.org/show_bug.cgi?id=727139
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=730129
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=730129
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=730129
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=730129
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the first page loaded in a webview would be done with
before the user had any chance to type an address, so it was safe to
assume that any typed address could be cleared during page loads,
as they would always come from previously loaded pages.
Now that the process of creating a webview is different and
involves spawning a web process that needs to be ready before
the initial page can be loaded, it might be possible for users
to type an address before this is ready. This breaks the previous
assumption and needs to be dealt with, in order to avoid
cleaning up typed text during the initial page load.
Additionally, it makes sense to make set_address() a no-op if
the given address is the same as the currently loaded.
https://bugzilla.gnome.org/show_bug.cgi?id=728143
|
|
|
|
|
|
|
|
| |
31bc1fe6 transformed a simple escape hatch of a comparison into an
assertion. But that assertion keeps getting triggered, so it's clearly
the wrong option for now.
https://bugzilla.gnome.org/show_bug.cgi?id=723909
|
|
|
|
|
|
| |
Should help with fixing bugs in an overzealous AdBlock.
https://bugzilla.gnome.org/show_bug.cgi?id=726883
|
|
|
|
|
|
|
|
|
|
| |
initial title
And use it from ephy-session so that when loading the session and not
using delayed requests, you don't see all the tabs initially with "Blank
Page" title.
https://bugzilla.gnome.org/show_bug.cgi?id=725649
|
|
|
|
|
|
|
| |
Since it's the embed title what it represents. The web view already has
a title property inherited from WebKitWebView.
https://bugzilla.gnome.org/show_bug.cgi?id=725649
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=725649
|
|
|
|
|
|
|
| |
The status message is actually a combination of the loading message and
link message, and both are already members.
https://bugzilla.gnome.org/show_bug.cgi?id=725649
|
|
|
|
|
|
|
|
| |
This is no longer used to set a loading title, since it's always called
with a URL or NULL. Also make it static since it's only used by
ephy-web-view.c. Remove the public getter since it's unused too.
https://bugzilla.gnome.org/show_bug.cgi?id=725649
|
|
|
|
|
|
|
|
|
| |
This is currently only used to set the window title and it's not
actually needed, since we don't show Loading string in title anymore,
only in the status bar. This is consistent with the title box and tabs
title.
https://bugzilla.gnome.org/show_bug.cgi?id=725649
|
|
|
|
|
|
|
| |
- fix regresion that broke CSS animation when removing items
- avoid user agent ul padding to affect grid centering
https://bugzilla.gnome.org/show_bug.cgi?id=724652
|
|
|
|
|
|
|
|
| |
New WebKit aborts the compilation if webkit2.h and
webkit-web-extension.h headers are included together. We are including
the ephy-web-extension.h header from the UI process only to get the
names of the dbus service, interface and path, so move those defines to
its own file that can be included by both UI and web process files.
|
|
|
|
|
|
|
|
|
| |
Now we query the history and snapshot services directly and the model is
used only in the web process. This fixes a race condition when the
overview page is created before the history query has completed leaving
an empty overview.
https://bugzilla.gnome.org/show_bug.cgi?id=725393
|
|
|
|
|
|
| |
ephy_embed_utils_address_has_web_scheme"
This reverts commit 8f441f2aa17bb2597753a44bb6d20cba24f71308.
|
|
|
|
|
|
| |
And use it only for actually typed (or pasted) text.
https://bugzilla.gnome.org/show_bug.cgi?id=725081
|
|
|
|
|
|
| |
has a web scheme
https://bugzilla.gnome.org/show_bug.cgi?id=725081
|
|
|
|
|
|
|
|
|
|
| |
Helper method used to check if a url is valid to decide whether to load
it or perform a search. It's mostly the same expression used by
EphyWebView, but moved to a helper function. The regular expressions used
in that expression are also moved to embed-utils and they are only
compiled once instead of everytime a web view is created.
https://bugzilla.gnome.org/show_bug.cgi?id=725081
|
|
|
|
|
|
|
|
| |
ephy_embed_utils_address_has_web_scheme
So that we don't need to do all the string comparisons always.
https://bugzilla.gnome.org/show_bug.cgi?id=725081
|
|
|
|
|
| |
Create the WebKitWebViewGroup object on demand when the first web view
is created.
|
|
|
|
|
| |
If the progressbar was already visible, we'd never really hide it.
Do it now.
|
|
|
|
|
|
|
| |
Use the original background color on about:epiphany
to fill all the page background.
https://bugzilla.gnome.org/show_bug.cgi?id=725245
|
|
|
|
|
|
|
|
| |
When the user removes an element, all instances of the overview
query the history service to be updated and insert the next
corresponding item.
https://bugzilla.gnome.org/show_bug.cgi?id=724697
|
|
|
|
|
| |
The default icon is now set in the css of the overview and it doesn't
need to be saved in the store.
|
|
|
|
|
|
|
| |
And use a link to the resource in the about pages instead of including
the file contents in the about page.
https://bugzilla.gnome.org/show_bug.cgi?id=724862
|
|
|
|
|
|
| |
And use it directly form the css using ephy-resource URI.
https://bugzilla.gnome.org/show_bug.cgi?id=724862
|
|
|
|
|
|
| |
Instead of decoding the image and send it to the web process.
https://bugzilla.gnome.org/show_bug.cgi?id=724862
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ideally we could use resource:// URIs since they are supported by both
WebKit and libsoup, but the web process doesn't have access to the
resources compiled in the UI process. And in multiprocess mode, the
network process doesn't have access to the resources either.
ephy-resource:// URIs are like a proxy to load gresources compiled in
the UI process, the data is sent directly to the web process in
single process mode or to the network process in multiprocess mode.
https://bugzilla.gnome.org/show_bug.cgi?id=724862
|
|
|
|
|
|
|
|
| |
about:applications
Pass the app icon filename instead.
https://bugzilla.gnome.org/show_bug.cgi?id=724862
|
|
|
|
|
|
| |
Pass the icon filename instead.
https://bugzilla.gnome.org/show_bug.cgi?id=724862
|
| |
|
| |
|
|
|
|
| |
variables
|
| |
|
|
|
|
| |
Now the title is correctly translated.
|
|
|
|
|
| |
It's currently unimplemented, we can bring it back eventually if we can
copy the back history and it's needed.
|
|
|
|
|
| |
And remove the automatic refresh when an overview item is removed via
javascript.
|
|
|
|
|
| |
Use the thumbnail path instead so that thumbnails are loaded in the web
process.
|
|
|
|
|
| |
It stores the path were the snapshot has been saved and notifies with a
signal when a new snapshot is saved in the cache.
|
| |
|
|
|
|
|
|
|
| |
Provides a basic alternative HTML implementation for the
overview, that can be accessed at 'about:html-overview'.
https://bugzilla.gnome.org/show_bug.cgi?id=723950
|