|
|
|
|
|
by olliej
973 days ago
|
|
First off, the share menu is an OS feature, not part of Safari. So this isn't Safari doing anything other than sending the URL to the share sheet, and the person has selected to share through a medium that allows previews. When you send a url through the share menu to a share extension that supports previews the share sheet needs to include: the title of page and a preview, and that's what's happening. Scraping the content from the currently open page would require the share sheet to be able to read state from the app triggering the send, or if the API allowed that app (safari in this case) to just include everything the app would need to do to a fresh request from an private context to give the best approximation of what the recipient would get, and so the "re-load of everything" would still be required. Finally, even if the app did want to use the existing page state, people seem to like the open graph meta tags that provide summary text or images which may not have been loaded, so they'd have to be requested instead. |
|