-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial qutebrowser support #1192
base: master
Are you sure you want to change the base?
Conversation
29bbe39
to
859b69d
Compare
859b69d
to
5b1e270
Compare
I got it to load on a test site (because all the sites I care about have properly restrictive content security policies that qutebrowser doesn't attempt to bypass) but it sits down in the corner and I can't exit insert mode. |
@toofar Thanks for trying this out (and congratulations for figuring out how to do it on your own!). Yep, there still are a few things to change regarding how the frame is inserted in the page, this is what I'm working on at this very moment :). Regarding CSPs, I think the most restrictive ones will remain an issue for Firenvim - the only way firenvim can work on fancy text editors is by inserting dynamically-genereted javascript in the page :/. |
@toofar The iframe should now be correctly placed over the textarea and qutebrowser should enter passthrough mode automatically. There's still a few tweaks I want to make, tests I want to perform and refactorings I want to do, so things aren't 100% done, but feel free to report other issues you might find :) |
@glacambre Hi! Any updates on this? |
@hirotasoshu Nope :). I've been pretty busy with other things and haven't had time to even work on the most important issue I have to tackle yet ( #1193 ), so qutebrowser support is unlikely to happen for now. Sorry! |
Closes #1190