We're deprecating vim modelines in favor of `.editorconfig`.
Removing vim modelines could be done using two one-liners. Most of the vim modelines
were followed by an empty line, so this one-liner took care of these ones:
```sh
rg '^# vim: .+\n\n' -l | xargs sed -i '/^# vim: /,+1d'
```
Then some of the vim modelines were followed by a pylint configuration line, so running
this one-liner afterwards took care of that:
```sh
rg '^# vim:' -l | xargs sed -i '/^# vim: /d'
```
The test file was taken from acid3, which does actually serve documents
for those locations.
For us, those documents never were available (as we're using `setHtml`
which uses a `data` URL internally), but the test does work just fine
without them. It was intended to test `appendChild` with different tags,
see the original commit (6c241f96ed) as
well as #2723 for details.
So far, them being there wasn't a problem, but with Qt 5.15.2 (or rather
the underlying Chromium 83), we get errors logged like this one:
"Invalid relative frame source URL (xhtml.3) within data URL.", source: (47)
So let's just not set them at all.
See #5752.
If we don't do this, when doing:
self.config_stub.val.content.user_stylesheets = css_path
then _update_stylesheet gets called before the stylesheet QWebEngineScript did
run (as there was no load yet), so we get:
[:2] Uncaught TypeError: Cannot read property 'stylesheet' of undefined!
Instead, load the page first and then update the stylesheet.
This tests that live updating works properly, and also makes sure we don't run
into the problem described above.
Florian Bruhin
Philipp Albrecht
Lembrun
Jay Kamat
Florian Bruhin