| Summary: | Extension frames fail to be embedded on websites | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Carlos J. <carlosj-webkit-bugzilla> |
| Component: | WebKit Extensions | Assignee: | Nobody <webkit-unassigned> |
| Status: | REOPENED --- | ||
| Severity: | Normal | CC: | ap, timothy, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Carlos J.
2022-10-17 04:51:54 PDT
Thank you for the report! This will continue to be tracked as a Safari issue, not a WebKit one. rdar://73826149 @alexey proskuryakov is there a clear line between what regards an issue as being a WebKit or a Safari issue? What is the scope of "WebKit Extensions" on bugs.webkit.org, and what issues should be reported elsewhere? Considering there is no browser UI present in this issue. The vast majority of extensions functionality is in Safari, not in WebKit. There is an occasional need to add or fix supporting code in WebKit. Tim will correct me if I'm wrong, but I'm guessing that this component is mostly for those issues filed by development team, not as much for reports. Tim tells me that it's fine to track these as open bugs in Bugzilla, in general. Yep, we are tracking bugs in Bugzilla for Web Extensions now as we move extensions support from Safari to WebKit. Just tested in Safari Technology Preview 192 and the issue is still there. |