rnhmjoj/qutebrowser
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Stop marking QtWebEngine as experimental

Browse Source
This commit is contained in:
Florian Bruhin 2017-06-30 10:42:33 +02:00
parent 0d5a33ef2a
commit e4a054d34e
2 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/qutebrowser.1.asciidoc
View File

@ -57,7 +57,7 @@ show it.
How URLs should be opened if there is already a qutebrowser instance running. How URLs should be opened if there is already a qutebrowser instance running.
*--backend* '{webkit,webengine}':: *--backend* '{webkit,webengine}'::
Which backend to use (webengine backend is EXPERIMENTAL!). Which backend to use.
*--enable-webengine-inspector*:: *--enable-webengine-inspector*::
Enable the web inspector for QtWebEngine. Note that this is a SECURITY RISK and you should not visit untrusted websites with the inspector turned on. See https://bugreports.qt.io/browse/QTBUG-50725 for more details. Enable the web inspector for QtWebEngine. Note that this is a SECURITY RISK and you should not visit untrusted websites with the inspector turned on. See https://bugreports.qt.io/browse/QTBUG-50725 for more details.

3
qutebrowser/qutebrowser.py
View File

@ -64,8 +64,7 @@ def get_argparser():
help="How URLs should be opened if there is already a " help="How URLs should be opened if there is already a "
"qutebrowser instance running.") "qutebrowser instance running.")
parser.add_argument('--backend', choices=['webkit', 'webengine'], parser.add_argument('--backend', choices=['webkit', 'webengine'],
help="Which backend to use (webengine backend is " help="Which backend to use.")
"EXPERIMENTAL!).")
parser.add_argument('--enable-webengine-inspector', action='store_true', parser.add_argument('--enable-webengine-inspector', action='store_true',
help="Enable the web inspector for QtWebEngine. Note " help="Enable the web inspector for QtWebEngine. Note "
"that this is a SECURITY RISK and you should not " "that this is a SECURITY RISK and you should not "