Extensions Click-to-Script: Automatically reload pages the user hasn't interacted with |
|
Issue descriptionExtensions that use the webRequest API or content scripts injecting at document_start or document_end need to refresh the page in order to work with click-to-script. Currently, we display an annoying "Need to refresh the page to continue" bubble. We should try automatically refreshing the page if the user hasn't interacted with something on it. As a first start, we could probably gate this on whether the user interacted with the page to enter form data. Another good signal could potentially be if the page has a beforeunload handler (which, if it did, would be a bit strange-looking to the user without any additional context).
,
Jul 10
Agreed - this could be a very jarring experience if we happen to miss a case where the user interacted heavily with the page. And this is also definitely something that can happen - I know I've seen web apps out there that don't properly store state or update the URLs on navigation. It's really mostly about which is better - without this, we'll have to prompt the user each and every time they click on an extension for the majority of extensions affected by click-to-script. I think that's probably, overall, worse than us getting this wrong occasionally - but it is a trade-off. > Are there other precedents of Chrome reloading the page without the user's explicit consent? Yep, tab discarding does this (we unload the page and reload it when the user refocuses it). They use the same logic proposed here. |
|
►
Sign in to add a comment |
|
Comment 1 by karandeepb@chromium.org
, Jul 9