qutebrowser/tests/unit/javascript
Jimmy b0d1a137da Greasemonkey: Don't attempt scope isolation on webkit
Since the JSCore used by WebKit 602.1 doesn't fully support Proxy and I
can't think of a way to provide isolation otherwise just revert to the
old behaviour in that case. I am checking for the specific WebKit
version because I'm pretty sure that version just happened to be
released when Proxy support was only partially done, any later release
will presumably have a newer JSCore where it works.

There I changed the indentation of a block in the jinja template which
will have inflated the diff.

I added mocking of `objects.backend` to the `webview` and
`webenginewebview` fixtures, I am pretty sure they are mutually
exclusive so don't expect any issues from that.

Because of the feature detection being at template compile time I had to
tweak the test setup to be done via a fixture instead of the setupClass
functionality that I was using before.
2018-05-20 18:42:40 +12:00
..
position_caret Remove unused imports 2018-03-19 19:42:56 +01:00
stylesheet Skip test_set_error entirely 2018-04-16 17:14:14 +02:00
base.html Reorganize tests directory. 2015-08-18 20:19:02 +02:00
conftest.py Log document.body in JS tests 2018-03-20 11:56:46 +01:00
test_greasemonkey.py Greasemonkey: Don't attempt scope isolation on webkit 2018-05-20 18:42:40 +12:00
test_js_execution.py Greasemonkey: Don't attempt scope isolation on webkit 2018-05-20 18:42:40 +12:00