www.star.fr layout issues

[q3cpma]

Version info (see :version):

qutebrowser v1.5.1
Git commit: 
Backend: QtWebEngine (Chromium 65.0.3325.230)

CPython: 3.6.5
Qt: 5.11.1 (compiled 5.9.6)
PyQt: 5.10.1

sip: 4.19.8
colorama: no
pypeg2: 2.15
jinja2: 2.10
pygments: 2.2.0
yaml: 3.13
cssutils: no
attr: 16.3.0
PyQt5.QtWebEngineWidgets: yes
PyQt5.QtWebKitWidgets: no
pdf.js: no
sqlite: 3.24.0
QtNetwork SSL: OpenSSL 1.0.2p  14 Aug 2018

Style: Qt5CTProxyStyle
Platform: Linux-4.18.14-gentoo-x86_64-AMD_FX-tm-8350_Eight-Core_Processor-with-gentoo-2.4.1, 64bit
Linux distribution: Gentoo/Linux (gentoo)
Frozen: False
Imported from /usr/lib64/python3.6/site-packages/qutebrowser
Using Python from /usr/bin/python3.6
Qt library executable path: /usr/lib64/qt5/libexec, data path: /usr/share/qt5

Paths:
cache: /home/user/.cache/qutebrowser
config: /home/user/.config/qutebrowser
data: /home/user/.local/share/qutebrowser
runtime: /tmp/runtime-user/qutebrowser

Description
When going to https://www.star.fr/ (with javascript enabled) and clicking on the button labeled "Préparer un itinéraire", a pane unfold under it, but it doesn't fully so (unlike with Firefox 60), making some important fields unreachable.

[The-Compiler]

I can reproduce this:

this JS error is logged:

[https://nmp-ihm.ctp.prod.canaltp.fr/fr/load/cM4Vcsgo/journey/?_=1539609193297:22] Uncaught SecurityError: Failed to read the 'localStorage' property from 'Window': Access is denied for this document.

Interestingly, it seems to work fine in KDE Falkon (though it sometimes needs two click to unfold)...

[q3cpma]

On Mon, Oct 15, 2018 at 01:22:51PM +0000, Florian Bruhin wrote: I can reproduce this:  this JS error is logged: ``` [https://nmp-ihm.ctp.prod.canaltp.fr/fr/load/cM4Vcsgo/journey/?_=1539609193297:22] Uncaught SecurityError: Failed to read the 'localStorage' property from 'Window': Access is denied for this document. ``` Interestingly, it seems to work fine in KDE Falkon (though it sometimes needs two click to unfold)... -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #4340 (comment)

I see. I tried looking at the page source but didn't thought about the console (probably because there are almost always massive amounts of warnings/errors on JS heavy MODERN WEBPAGE^tm).