For some reason, populating the text (even if we completely overwrite
it later) before the highlighter is added results in no highlighting.
I think this has something to do with python locking/delayed
re-highlighting.
At some point, it would be nice to file this as a bug, but I can't
seem to make a small c++ example.
See https://codereview.qt-project.org/#/c/244699/4//ALL and
https://bugreports.qt.io/browse/QTBUG-71307 for more information.
Closes#4519
Changes to be committed:
modified: qutebrowser/browser/browsertab.py
modified: qutebrowser/config/configdata.yml
modified: tests/end2end/features/tabs.feature
Changed pinned.tabs.frozen to be tabs.pinned.frozen in all of
these files.
Implement a new setting, `pinned.tab.frozen` (boolean), which when false
allows a user to navigate to new URLs in a pinned tab (default behavior
is to have `pinned.tab.frozen = true`, in which no navigation is allowed).
issue URL: https://github.com/qutebrowser/qutebrowser/issues/4400
Changes to be committed:
modified: qutebrowser/browser/browsertab.py
Add `navigation_blocked` method to AbstractTab, which returns
true if navigation is allowed on a tab.
modified: qutebrowser/browser/commands.py
Change `openurl` to use `navigation_blocked` method of a tab to
determine behavior while navigating a pinned tab.
modified: qutebrowser/components/misccommands.py
Change `home` to use `navigation_blocked` method of a tab to
determine behavior while navigating a pinned tab.
modified: qutebrowser/config/configdata.yml
Add `pinned.tab.frozen` config.
modified: tests/end2end/features/tabs.feature
Add tests for :open and :home on pinned tabs with
`pinned.tab.frozen` set to false
