| Summary: | [WPE][GTK] Add WebKitWebExtension API to indicate web extension does not link to GPL code, and use it to gate WebRTC access (?) | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | WebRTC | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | bugs-noreply, jan.brummer, mcatanzaro, pnormand, youennf |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | PC | ||
| OS: | Linux | ||
|
Description
Michael Catanzaro
2020-07-26 14:04:57 PDT
Why not extend webkit_settings_new_with_settings ? WebKitSettings is a UI process API, whereas WebKitWebExtension corresponds perfectly to actual web extension shared objects. The UI process might not know which web extensions are going to be in use. In fact, if you write a custom web extension and install it into Epiphany's web extensions dir, WebKit will happily load it. That would be a strange thing to do, definitely not supported, but if you want to write GPL a web extension that, say, changes all text color to red, you can do it. Ok, thanks for the info. Closing this. The worry is that dlopening libwebrtc would be a lot of work and it would be simpler to just proceed with plans for gst-webrtc instead. |