Bug 246617 - Extension frames fail to be embedded on websites
Summary: Extension frames fail to be embedded on websites
Status: REOPENED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Extensions (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-10-17 04:51 PDT by Carlos J.
Modified: 2024-04-23 06:38 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos J. 2022-10-17 04:51:54 PDT
Trying to put a view (html page) from a web extension into an iframe on a website. The html file is listed correctly in web_accessible_resources, however when I'm trying to load it, I get the following error: Failed to load resource: The operation couldn’t be completed. (Cocoa error -1008.)

Sample extension can be found here:
https://github.com/carlosjeurissen/webext-tech-demo-extensions/tree/main/issues/safari-8986072-frame-extension-on-website

In browsers like Firefox and Chrome. The frame is loaded and says "frame". In Safari it doesn't load and thus is blank.

Previously reported as:
https://feedbackassistant.apple.com/feedback/8986072
https://developer.apple.com/forums/thread/672746
Comment 1 Alexey Proskuryakov 2022-10-17 10:32:37 PDT
Thank you for the report! This will continue to be tracked as a Safari issue, not a WebKit one.

rdar://73826149
Comment 2 Carlos J. 2022-10-18 06:28:49 PDT
@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.
Comment 3 Alexey Proskuryakov 2022-10-18 09:25:19 PDT
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.
Comment 4 Alexey Proskuryakov 2022-10-24 13:22:32 PDT
Tim tells me that it's fine to track these as open bugs in Bugzilla, in general.
Comment 5 Timothy Hatcher 2022-10-24 13:30:00 PDT
Yep, we are tracking bugs in Bugzilla for Web Extensions now as we move extensions support from Safari to WebKit.
Comment 6 Carlos J. 2024-04-23 06:38:28 PDT
Just tested in Safari Technology Preview 192 and the issue is still there.