Matt Huggins
Matt Huggins
Ahh, I know why. We're always passing the action data & error to the component. This, combined with the fact that spunky doesn't clear out prior errors/data unless a new...
Thanks for submitting this!
It seems like we may not have the option to make this work. According to [this article](https://davidwalsh.name/browser-camera): > Browser vendors have recently ruled that getUserMedia should only work on https:...
It looks like we can register a protocol as "secure" in electron. So in theory, we could change this line: https://github.com/nos/client/blob/321dbf26928380bc0b6affb0aca70830f0a3c053/src/main/index.js#L19 to instead read: ```js protocol.registerStandardSchemes(['nos'], { secure: true });...
@deanpress I think we should opt to close this and #345 given the above, but I wanted to see what you think. Users will still be able to use `getUserMedia`...
A possible solution for content hosted coming from the `nos` protocol would be to communicate with an IFRAME that's using the `https` protocol via [cross-origin communication](https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage).
@jeroenptrs Interesting idea. Where is this being used today? Would it integrate well with neon-js by chance?
If we can make this work with neon-js, then that might be a good short-term solution. The downside is that it's a centralized solution. It seems like this is something...
This needs design. /cc @fabric-8
We're seeing this error crop up in some sidekiq jobs.