Per-view user toggle to adjust power preference for model

Elsewhere, @mehmetoguzderin wrote:

Progressive loading of media content is the same for almost all media types, and users can simply stop loading pages to avoid further data use. But going 3D, another dimension for progressive refinement comes along, which is the render's improvement over time. Although the idea of "maybe sites should avoid deploying costly scenes which hardware is under capable" is sound, people will likely want to display scenes that consist of content that creates a huge overhead even after the fetch from remote (which is the analogous part of progressive loading for the model that user can cancel already), increase of high-frequency detail in 3D content is a well-known trend, and people will want more of it when catering to a wider audience which might not be happy with blurry or under-defined regions.

In such scenarios, many techniques like upscaling, reducing samples per render (not only per pixel) exist that make it possible to improve time-to-first-display and increase fidelity over time. Browsers can ultimately deploy these to be more inclusive of challenging content. But this can come with a significant power draw. I think it might suit users' interest if the model can support a per-view (user might want a view to be improving but not the others) power preference toggle, which could hint browsers to drop any further refinement.

Start with the issue body and the linked WebKit explainer discussion to understand the proposed per-view power preference. No files, tests, or entry points are named; done would require an agreed design for the toggle and its effect on further model refinement.