Re: [crx] Inspect popup unavailable since latest version of chrome

[CGS]

Open the popup, click right on it and select inspect element.

CGS

On Mon, Aug 20, 2012 at 6:35 PM, Pierre Tardy <tar...@gmail.com> wrote:

Hello,
I used to right click on my extension icon, in order to debug it.

I just tried it today to fix some bug, and it does not show anymore.
I tried on both windows and linux version of chrome (21.0.1180.79 m), of course I have developer mode enabled.

Any clue?

Regards,
Pierre

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/f90hguItg50J.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.

[Pierre Tardy]

On Tue, Aug 21, 2012 at 11:43 AM, CGS <cgsmc...@gmail.com> wrote:

Open the popup, click right on it and select inspect element.

Thanks, the doc is not up-to-date..

This is painful, as you cannot put breakpoints on your "onload" JS anymore :-(

Pierre, having very hard time converting his dojo based extension to the sandboxed system.

[Abraham Williams]

You can still put breakpoints in onload and execute location.reload() in the console.

Abraham
--
Abraham Williams | abrah.am | abraham+ | addvocate.co

@abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

[Joe Marini]

Exactly. The console process still works fine.

[PhistucK]

Sounds like something that would not be resolved using that "Inspect Popup" feature.

Do you have a "default_popup" key within your manifest?

(Just "popup" is no longer supported in manifest version 2)

☆PhistucK

On Wed, Sep 5, 2012 at 6:25 AM, Aegist <bookm...@gmail.com> wrote:

This seems like a really really bad change to me, maybe just because of the problem I am currently having:
When I click on my plugin, the popup isn't appearing. So now I can't inspect it at all.

Anyone got any ideas on how to get around that?

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/G4eflpBxAh0J.

[Godmar Back]

I know you can inspect the popup once it's open, but as you point out that wouldn't be helping if the popup isn't showing at all.

Related question: is it possible to set breakpoints in JavaScript code that's executed before the popup reaches the DOM ready state?

 - Godmar

On Tue, Sep 4, 2012 at 11:25 PM, Aegist <bookm...@gmail.com> wrote:

This seems like a really really bad change to me, maybe just because of the problem I am currently having:
When I click on my plugin, the popup isn't appearing. So now I can't inspect it at all.

Anyone got any ideas on how to get around that?

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/G4eflpBxAh0J.

[Joe Marini]

That should be possible - just set the breakpoints in the JS code, then use the console to call location.reload().

--
Joe Marini

Developer Advocate / Chrome

joem...@google.com | +Joe Marini | @joemarini

[PhistucK]

Or use the debugger; statement.

☆PhistucK

[doubleTap]

In your browser go to chrome-extension://yourExtensionIDHere/data/pop.html