diff options
| author | Patrick McDermott <pj@pehjota.net> | 2017-09-17 05:07:42 (EDT) |
|---|---|---|
| committer | Patrick McDermott <pj@pehjota.net> | 2017-09-17 05:07:42 (EDT) |
| commit | aef05e105fb157d8856863c7858d1ce596bd6f2e (patch) | |
| tree | fb8b5f7d2b67ed904979078987a64527aa04c9e9 /src/window.c | |
| parent | e8507a09988fb4307051d34fb5facf8621df3e7e (diff) | |
| download | marquee-aef05e105fb157d8856863c7858d1ce596bd6f2e.zip marquee-aef05e105fb157d8856863c7858d1ce596bd6f2e.tar.gz marquee-aef05e105fb157d8856863c7858d1ce596bd6f2e.tar.bz2 | |
src/tab-chrome.[ch]: Hack around progress bar issue
If loading fails, the WebKitWebView's "estimated-load-progress" is set
to 1.0 after signals like "load-changed" and "load-failed" are emitted.
So the only way to avoid leaving behind a full progress bar after, for
example, canceling a page load is to save a flag on a failed load and
only update the progress bar if the flag is unset.
Diffstat (limited to 'src/window.c')
0 files changed, 0 insertions, 0 deletions