diff options
| author | Florian Bruhin <me@the-compiler.org> | 2021-03-12 10:42:00 +0100 |
|---|---|---|
| committer | Florian Bruhin <me@the-compiler.org> | 2021-03-12 10:42:00 +0100 |
| commit | dfe5a3789c5833c3e6313f708661b22048d6a5e2 (patch) | |
| tree | e55578ba1d07fa836d5a18a2cc22a1d6913a6a6c | |
| parent | 6de5431d2ce35907aa0685f00f36d7f5a1b0866c (diff) | |
| download | qutebrowser-dfe5a3789c5833c3e6313f708661b22048d6a5e2.tar.gz qutebrowser-dfe5a3789c5833c3e6313f708661b22048d6a5e2.zip | |
Update session warning
See #5359
| -rw-r--r-- | qutebrowser/html/warning-sessions.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/qutebrowser/html/warning-sessions.html b/qutebrowser/html/warning-sessions.html index d297a2656..422b409a9 100644 --- a/qutebrowser/html/warning-sessions.html +++ b/qutebrowser/html/warning-sessions.html @@ -9,7 +9,7 @@ qute://warning/sessions</span> to show it again at a later time.</span> <p>Since Qt doesn't provide an API to load the history of a tab, qutebrowser relies on a reverse-engineered binary serialization format to load tab history from session files. With Qt 5.15, unfortunately that format changed (due to the underlying Chromium upgrade), in a way which makes it impossible for qutebrowser to load tab history from existing session data.</p> -<p>At the time of writing (January 2021), a new session format which stores part of the needed binary data in saved sessions is <a href="https://github.com/qutebrowser/qutebrowser/issues/5359">in development</a>. However, it unfortunately wasn't ready in time for qutebrowser v2.0.0, as it's a rather big refactoring. It's currently expected to be released as part of qutebrowser v2.1.0.</p> +<p>At the time of writing (January 2021), a new session format which stores part of the needed binary data in saved sessions is <a href="https://github.com/qutebrowser/qutebrowser/issues/5359">in development</a>. However, it unfortunately wasn't ready in time for qutebrowser v2.0.0, as it's a rather big refactoring. It's currently expected to be released in a future v2.x.0 release.</p> <p>As a stop-gap measure:</p> |