Testshell + Flash plugin on Mac OS...

[amitkishnani]

Hey Guys,

1. i synced to 10.0.648.127 stable release : http://src.chromium.org/svn/releases/10.0.648.127/
2. build on MacOS in XCode
3. when i launched the test-shell with browse to page : "http://
www.adobe.com/software/flash/about/"

it rendered the html but the flash area appears to be white or blank ,
i can right click and it shows the flash plugin context menu

it just not rendering for Testshell on Mac , it works fine on windows.

any ideas ? , is flash plugin rendering supported with testshell on
Mac or am i missing some launch/start parameter ?

thanks,
Amit

[Stuart Morgan]

Le 17 mars 2011 17:53, amitkishnani <akis...@gmail.com> a écrit :
> any ideas ? , is flash plugin rendering supported with testshell on
> Mac or am i missing some launch/start parameter ?

Plugins on the Mac are largely non-functional when run in-process, as
is done in testshell. There's no real plan to make them work correctly
in that mode, since IIRC correct support would require changes to
fundamental assumptions about the way threading works for in-process
plugins in Chrome.

-Stuart

[amitkishnani]

Stuart,

thanks for confirming, i was wondering - if it was something i was
missing at my end.

i have a follow-up question, it does appear in-process plugins work
fine on Windows-OS since the test_shell renders flash content fine on
windows when run in-process mode, so is the below behavior of "in-
process" plugins not rendering tied to Mac only ?

thanks,
Amit

On Mar 18, 8:45 am, Stuart Morgan <stuartmor...@chromium.org> wrote:

[Stuart Morgan]

Le 18 mars 2011 11:34, amitkishnani <akis...@gmail.com> a écrit :
> i have a follow-up question,  it does appear in-process plugins work
> fine on Windows-OS since the test_shell renders flash content fine on
> windows when run in-process mode,  so is the below behavior of "in-
> process" plugins not rendering tied to Mac only ?

Not rendering, specifically, is probably only true of certain plugin
drawing models on the Mac. Not being supported/working in general is
true of Mac, and I believe Linux as well. On the Mac the fundamental
problem is that plugins *must* run on the UI thread, unlike Windows
where they can have a separate thread, and Chrome isn't designed to
share its UI thread with plugins. My recollection is that the same is
true of Linux.

-Stuart

[amitkishnani]

Stuart,

when you are refering to "Chrome isn't designed to share its UI thread
with plugins", i assume that is also true for "testshell" app.

does flash & other plugins get launched in their own thread when run
in-process mode as in testshell ? , in other words do plugins get
their own thread or it varies from plugin to plugin to spawn its own
thread, i did not see the code in test_shell/webkit creating a
separate thread for each plugin instantiation - but i could be
wrong..?

thanks,
Amit

On Mar 18, 11:59 am, Stuart Morgan <stuartmor...@chromium.org> wrote:

[Stuart Morgan]

Le 18 mars 2011 13:19, amitkishnani <akis...@gmail.com> a écrit :
> does flash & other plugins get launched in their own thread when run
> in-process mode as in testshell ?

It's not a thread per plugin, it's a question of whether plugins are
run on the UI thread, or another thread. I don't remember all the
details though, since most of my plugin work was after it became clean
that in-process was problematic on the Mac; maybe someone who knows
more about the in-process plugin model will chime in here.

-Stuart