[Webkit-unassigned] [Bug 238151] New: Safari Web Extensions & Content blockers not working when a standalone website gets added to homescreen

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=238151

            Bug ID: 238151
           Summary: Safari Web Extensions & Content blockers not working
                    when a standalone website gets added to homescreen
           Product: WebKit
           Version: Safari 15
          Hardware: iPhone / iPad
                OS: iOS 15
            Status: NEW
          Severity: Major
          Priority: P2
         Component: WebKit API
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: daniyaldehleh at gmail.com

Feedback number: FB9945101

The Safari extension works well when the user is in Safari & adds the Safari page to homescreen. However, if the website page has "Display":"Standalone" on which is best practice for companies to use to give app like experience to user per their expectation (just like the instagram video) does, the safari extension then crashes or stops running immediately despite at the end of the day being a Safari page just like with Youtube. However, it's the extension runs on youtube as they've not implemented the best practice or standalone in their manifest file shouldn't seem to affect extension & their purpose per user permission & expectation at the end of the day.

The same goes for content blockers. However, with content blockers, when it comes applying rules (blocking) they work even in standalone, however, when it comes to removing the they don't despite reloading the extension in both cases.

Feedback number: FB9959459

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220321/d0e8b156/attachment.htm>