You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
qt: fix cam access by restoring window.isSecureContext
In d78380f, we switched from qrc:/ to the bitboxapp:/ custom scheme
so we can force mimetypes in the scheme handler. This somehow made
window.isSecureContext be false, breaking camera (which requires a
secure context).
The issue was that our scheme handler was never registered, because it
was configued with HostAndPort but no default port was specified. We
could specify one, or switch to Host only, but in our case Path seems
to be most appropriate.
The frontend navigation is changed from browser router to hash based
router, as somehow navigation breaks in the custom scheme, as the
frontend tries to actually request the individual pages from
QtWebEngine. Not sure why it was working before or what causes it, but
a local hash based router seems to work.
0 commit comments