On Tue, 23 Mar 2010, 05:53:23 GMT, Wu, Yong <[email protected]> wrote:
>
[Snip]
> 5, We enter the native rendering in the following four
> scenarios: a) automatically enter native rendering for any full-screen
> objects,
> for instance PDF or full screen video display. b) automatically enter native
> rendering when the dominant viewport of user content view is a plugin window,
> esp, user are watching a flash video.
These heuristics sound good. Does "dominant" mean >50%?
> c) suggest to enter native rendering mode
> when there is embedded Java/flash plugins. This will enable Java plugins and
> improve flash performance. d) at any time, user could choose to enter/leave
> native rendering manually (via a toolbar button).
As you say, the difference to a user will be obscure, any toolbar button will
just become "that button which makes YouTube a bit better but breaks
scrolling". I'm also worried about the prompt when there are embedded plugins:
there's a lot of useless Flash around the web which'd trigger it for a lot of
pages.
Perhaps any exposure of it in the UI could be avoided with additional
heuristics:
c) Enter native mode when there are embedded plugins larger than
300x200 (or some %ge) in the viewport and the user hasn't
interacted with the browser (rather than the plugin) in
5 seconds.
d) Enter native mode when a plugin gets focused/clicked on
and go back to tiled mode when the container gets it
back.
Comments welcome :)
Cheers,
Andrew
--
Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
