3 ms·
That would be amazingly slow to call an out of process function on each match when the page renders. Extensions run as a separate process. I would be amazed if
by scarface74 7y ago
That would be amazingly slow to call an out of process function on each match when the page renders. Extensions run as a separate process. I would be amazed if Apple would allow something that inefficient as careful as it is about battery and memory efficiency.
- saagarjha 7y agoI mean, the Safari application is already doing XPC with the web content process constantly anyways. And perhaps they can batch these messages?
- scarface74 7y agoWhy would Safari be doing any communication with the content blockers? The content blockers are submitting JSON one time to iOS Safari and aren’t running at all.
- saagarjha 7y agoThe Safari App Extension is running in the background, which is presumably what the process is communicating with.
- scarface74 7y agoYou’re talking about MacOS and not iOS? As far I know, the only time Safari or any other app on iOS calls an extension is when the user chooses to “share” with that extension
- saagarjha 7y agoYeah, I think this API is only available on macOS. On iOS this would require keeping the extension alive in the background, which Apple seems largely opposed to allowing.