It was a common tool for "clickjacking" experiments, where a refresh could reset the state of a transparent overlay. Why was it patched?
The standard XFO (X-Frame-Options) or CSP headers are now being strictly enforced, even during a forced refresh. viewerframe mode refresh patched
By refreshing the viewer state, certain inline script blocks could occasionally be re-evaluated under different security contexts. It was a common tool for "clickjacking" experiments,
If you need to communicate between a parent and a child frame, use the window.postMessage API. It is the secure, modern standard. By refreshing the viewer state, certain inline script
In some edge cases, it allowed content to be "framed" even when the server strictly forbade it.
ViewerFrame (often associated with specific legacy browser modes or internal frame-handling protocols) allowed developers—and sometimes attackers—to manipulate how a page refreshed or loaded content within a frame.