My favorites ▼ | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 46871: After reloading an extension, the developer tools are reloaded and switched to the Elements tab
1 person starred this issue and may be notified of changes. Back to list
 
Reported by kcbanner, Jun 17, 2010 
Chrome Version       : 6.0.437.1 (Official Build 49781) dev

What steps will reproduce the problem?
1. Open Developer Tools for an extension page (such as background.html). Switch to a tab other than Elements.
2. Reload the extension.
3. Developer Tools will now reload and switch to the Elements tab.

What is the expected result?
The developer tools will remain on the tab that was selected before reload.

What happens instead?
The developer tools switch to the Elements tab.

Please provide any additional information below. Attach a screenshot if
possible.

Is this intended? As an extension developer, this is a minor annoyance. I frequently reload my extension during development and prefer to use the Console tab, so I have to constantly switch.
Jun 21, 2010
#1 stuartmorgan@chromium.org 
(No comment was entered for this change.)
Labels: -Area-Undefined Area-UI Feature-DevTools
Jan 27, 2011
#2 pfeld...@chromium.org 
(No comment was entered for this change.)
Status: Assigned
Owner: ca...@chromium.org
Labels: Mstone-11
Mar 9, 2011
#3 kar...@google.com 
rolling non releaseblocker mstone 11 bugs to mstone 12.
Labels: -Mstone-11 MovedFrom-11 Mstone-12
Apr 25, 2011
#4 kerz@google.com 
Moving out of M12.
Labels: Mstone13 MovedFrom12
Apr 25, 2011
#5 kerz@google.com 
Moving out of M12.
Labels: -Mstone-12 Mstone-13
Jun 2, 2011
#6 lafo...@chromium.org 
Moving !type=meta|regression and !releaseblocker to next mstone
Labels: -Mstone-13 Mstone-14 MovedFrom13
Jun 2, 2011
#7 lafo...@chromium.org 
(No comment was entered for this change.)
Labels: -MovedFrom12 MovedFrom-12
Jul 27, 2011
#8 kerz@google.com 
Punting out non-critical bugs.  Please move back to 14 if you believe this was done in error.
Labels: -Mstone-14 Mstone-15 MovedFrom-14
Sep 8, 2011
#9 kar...@google.com 
moving non-essential bugs from 15 to 16. Please feel free to move back if this is an error and your bug is a blocker for 15.
Labels: Mstone-16 MovedFrom15 bulkmove
Oct 22, 2011
#10 pfeld...@chromium.org 
(No comment was entered for this change.)
Labels: -MovedFrom-11 -Mstone13 -MovedFrom13 -MovedFrom-12 -MovedFrom-14 -Mstone-16 -MovedFrom15 -bulkmove Mstone-18
Feb 7, 2012
#11 kar...@google.com 
(No comment was entered for this change.)
Labels: MovedFrom18 Mstone-19
Mar 27, 2012
#12 lafo...@google.com 
(No comment was entered for this change.)
Labels: -Mstone-19 Mstone-20 MovedFrom-19
May 4, 2012
#13 dhar...@google.com 
(No comment was entered for this change.)
Labels: -Mstone-20 bulkmove MovedFrom-20 Mstone-21
Jul 11, 2012
#14 ka...@chromium.org 
Moving all non essential bugs to the next Milestone
Labels: -Mstone-21 MovedFrom-21 Mstone-22
Aug 30, 2012
#15 kerz@google.com 
Moving all non-blocking 22 issues to 23.
Labels: -Mstone-22 MovedFrom-22 Mstone-23
Oct 10, 2012
#16 ka...@chromium.org 
Moving all non essential bugs to the next Milestone
Labels: -Mstone-23 MovedFrom-23 Mstone-24
Nov 5, 2012
#17 dhar...@google.com 
Since the bug has moved few times, removing the milestone label. Please target the right milestone.
Labels: -Mstone-24
Mar 10, 2013
#18 bugdroid1@chromium.org 
(No comment was entered for this change.)
Labels: -Area-UI -Feature-DevTools Cr-Platform-DevTools Cr-UI
► Sign in to add a comment

Powered by Google Project Hosting