Closed adbenitez closed 9 months ago
we would need to upgrade electron for this or get rid of the iframe (FILL 500 hack)
this requires electron 25+
get rid of the iframe (FILL 500 hack)
How would that work? I see that the wrapper is still used in #3381.
It looks to me like this piece of code does nothing, after the introduction of the WebRTC exfiltration mitigation:
Because all navigation is prevented anyway:
I might be wrong though.
We need to either get rid of the frame again or use an electron version that has the "will-frame-navigate" event.
Someone could also attempt to backport the event to electron 22, but that might be to complicated.
How does "will-frame-navigate"
help?
We want an <iframe>
because:
RTCPeerConnection
at all times while the user script is active.Does the new Electron allow to solve the reload problem?
How does "will-frame-navigate" help?
It allows us to use the code you mentioned in your previous comment again. Or have I missed something?
Yeah, for "will-frame-navigate" that's true (I think), but I'm asking about how it's gonna help get rid of the wrapper <iframe>
.
It won't, I said we "either" need one or the other, not both.
Oh I see. How does the new Electron version allow to get rid of the 500 hack then?
How does the new Electron version allow to get rid of the 500 hack then?
no, this is just about the mailto:
stuff discussed in this issue.
My communication seems lacks here, please tell me how to improve it.
Ok, it's my bad, sorry 🤦♀️ I read
we would need to upgrade electron for this or get rid of the iframe (FILL 500 hack)
as "for this to get rid". I thought you have an idea of how to get rid of the <iframe>
, it's why I keep asking.
looks like we did not even need the electron upgrade, in the end it was contents.setWindowOpenHandler()