Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8310661
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T19:32:27+00:00 2026-06-08T19:32:27+00:00

To debug extensions, Chrome used to have a Inspect popup menu option available when

  • 0

To debug extensions, Chrome used to have a “Inspect popup” menu option available when right clicking the extension icon (top right in the browser). I believe this options was recently removed (possibly with the latest Chrome version 20, which I am using) .

The debug console can still be activated by right clicking any element in the extension popup and selecting “Inspect element”. The problem I am experiencing however is that whenever I now have the debug console open, typing into form elements in the popup does not work. Even though the form element seems to have the focus (it has a blinking cursor active), all input typed goes straight to the debug console.

Update: It seems focus is not specifically to the debug console, but to whichever window is below. It’s like the extension window is a “stay on top” window, without capturing any input.

Update: 2012-07-24: Updated to 22.0.1215.0 (Official Build 147830) dev and the bug is still there. But yay, Youtube full screen now suddenly works on my dual screen system!

Update 2012-05-09: Upgraded from 20.0.1123 to 20.0.1130.1 dev on Linux x64 (Ubuntu 12.04). Problem still there, and makes debugging extensions a lot harder than needs be. Also confirmed behaviour on older Chrome release (20.0.1105.0). Oh well, maybe it’s just me…

Update 2012-05-09 2: Assuming this is a bug, consider adding a background page to your popup and log to that page’s console instead until bug gets fixed. At least that makes my life easier for now.

Update: 2012-10-19: As omri writes (and points to), the Inspect Popup option is on it’s way to be put back into Chrome, which will hopefully solve this problem (finally).

Could anybody confirm/deny this behavior, and/or suggest possible workarounds?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T19:32:32+00:00Added an answer on June 8, 2026 at 7:32 pm

    Just upgraded to 22.0.1221.1 (Official Build 149058) dev and the problem seems to have been solved, albeit with a workaround. The old way of right clicking in the popup window and selecting “Inspect Element” to start up the console still grabs all input as originally reported.

    However, it seems by right clicking the popup icon, the old “Inspect Popup” seems to be back, and when this is used it does not seem to grab input from the open popup window itself.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm working on a Google Chrome extension. In the popup I have the following
I am creating a Chrome Extension that upon clicking the extension icon will present
I am attempting to set up a chrome extension similar to http://code.google.com/chrome/extensions/trunk/samples.html#webrequest except that
I can use chrome's inspect element feature to view and debug my javascript, but
I'm making a Chrome Extension and need to view the HTML/CSS/JS of the popup.html
I'm creating (learning) an extension for Google Chrome. To debug some code, I inserted
I am trying to break execution with Debug points in a Visual Studio extension
Debug HTTP is easy, you have all sort of tools to do it (like
Debug mode in MigLayout is quite powerful option for development and debugging. It is
i am beginner with chrome extension.There is simple problem. There is the code in

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.