WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED MOVED
238151
Safari Web Extensions & Content blockers not working when a standalone website gets added to homescreen
https://bugs.webkit.org/show_bug.cgi?id=238151
Summary
Safari Web Extensions & Content blockers not working when a standalone websit...
Daniyal
Reported
2022-03-21 13:44:55 PDT
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
Attachments
Add attachment
proposed patch, testcase, etc.
Sam Sneddon [:gsnedders]
Comment 1
2022-07-04 20:40:59 PDT
Both of these are issues within Safari and not within WebKit.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug