You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by mark goldin <ma...@gmail.com> on 2015/04/03 18:27:11 UTC
Chrome for debugging
I am trying to follow Adobe instructions how configure Chrome for Flash
debugging but it is still not working for me. I have downloaded the
debugging version ver. 17 for Oepra and Chromium applications). Then
disabled the stock one and enabled the debugging version. Still no luck.
Any idea?
Thanks
Re: Chrome for debugging
Posted by Paul Hastings <pa...@gmail.com>.
On 4/5/2015 11:31 PM, Mark Line wrote:
> I tend to use FF for dev (debug player) and keep chrome with the pepper
> player for normal use
i've had to do that as well. the latest versions of the pepper debugger hang
constantly at breakpoints & after loading a module. its kind of a heart breaker.
Re: Chrome for debugging
Posted by Mark Line <ma...@gmail.com>.
Don't think you can turn it off in chrome. In Firefox you can turn the time
out off.
I tend to use FF for dev (debug player) and keep chrome with the pepper
player for normal use
On 5 Apr 2015 11:46 am, "mark goldin" <ma...@gmail.com> wrote:
> Exactly what I did. Everything is working fine except when I am in
> debugging mode sitting on a break point I am getting a message from Chrome
> that plug-in is unresponsive and if I want to continue waiting. Is there
> something can be done about it?
>
> Thanks
>
> On Sat, Apr 4, 2015 at 1:53 PM, Evyatar Ben Halevi-Arbib <
> evyatarbh@gmail.com> wrote:
>
> > Download the Firefox NPAPI debugger version and use that instead of the
> > PPAPI versions.
> >
> > Good luck,
> > Evyatar
> > בתאריך 3 באפר 2015 19:29, "mark goldin" <ma...@gmail.com> כתב:
> >
> > > I am trying to follow Adobe instructions how configure Chrome for Flash
> > > debugging but it is still not working for me. I have downloaded the
> > > debugging version ver. 17 for Oepra and Chromium applications). Then
> > > disabled the stock one and enabled the debugging version. Still no
> luck.
> > > Any idea?
> > >
> > > Thanks
> > >
> >
>
RE: Chrome for debugging
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi,
Until that date I'll be happy to continue to use the NPAPI plugin in Chrome and I would like they do something about the limited sandbox of the PPAPI but from what I read it is not about to happen, they even questioning the well founded of the the local sandboxing approach preferring IIRC the use of a local web server to serve the files [1] which is not a handy at all solution at developer point of view.
Frédéric THOMAS
[1] https://forums.adobe.com/message/6945735#6945735
> Date: Tue, 21 Apr 2015 05:01:36 -0700
> From: yishayjobs@hotmail.com
> To: users@flex.apache.org
> Subject: Re: Chrome for debugging
>
> |Since a recent update you won't be able to see your npapi plugin in
> chrome://plugins unless you navigate to the following
>
> chrome://flags/#enable-npapi
>
> This workaround will not be available starting November 2015.
>
> Hopefully Adobe can make their pepper debug version functional before that
> date.
>
> The following article explains it.
>
> https://www.chromium.org/developers/npapi-deprecation
>
>
>
> --
> View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Chrome-for-debugging-tp10001p10138.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Chrome for debugging
Posted by Yishay Weiss <yi...@hotmail.com>.
|Since a recent update you won't be able to see your npapi plugin in
chrome://plugins unless you navigate to the following
chrome://flags/#enable-npapi
This workaround will not be available starting November 2015.
Hopefully Adobe can make their pepper debug version functional before that
date.
The following article explains it.
https://www.chromium.org/developers/npapi-deprecation
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Chrome-for-debugging-tp10001p10138.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Chrome for debugging
Posted by mark goldin <ma...@gmail.com>.
Exactly what I did. Everything is working fine except when I am in
debugging mode sitting on a break point I am getting a message from Chrome
that plug-in is unresponsive and if I want to continue waiting. Is there
something can be done about it?
Thanks
On Sat, Apr 4, 2015 at 1:53 PM, Evyatar Ben Halevi-Arbib <
evyatarbh@gmail.com> wrote:
> Download the Firefox NPAPI debugger version and use that instead of the
> PPAPI versions.
>
> Good luck,
> Evyatar
> בתאריך 3 באפר 2015 19:29, "mark goldin" <ma...@gmail.com> כתב:
>
> > I am trying to follow Adobe instructions how configure Chrome for Flash
> > debugging but it is still not working for me. I have downloaded the
> > debugging version ver. 17 for Oepra and Chromium applications). Then
> > disabled the stock one and enabled the debugging version. Still no luck.
> > Any idea?
> >
> > Thanks
> >
>
Re: Chrome for debugging
Posted by Evyatar Ben Halevi-Arbib <ev...@gmail.com>.
Download the Firefox NPAPI debugger version and use that instead of the
PPAPI versions.
Good luck,
Evyatar
בתאריך 3 באפר 2015 19:29, "mark goldin" <ma...@gmail.com> כתב:
> I am trying to follow Adobe instructions how configure Chrome for Flash
> debugging but it is still not working for me. I have downloaded the
> debugging version ver. 17 for Oepra and Chromium applications). Then
> disabled the stock one and enabled the debugging version. Still no luck.
> Any idea?
>
> Thanks
>