Closed Bug 843560 Opened 12 years ago Closed 12 years ago

web console should be opened via element inspector

Categories

(DevTools :: Console, defect)

18 Branch
x86_64
Windows 8
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: leonardo.balter, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 Build ID: 20130201065344 Steps to reproduce: - Right click on any opened page - clicked on "Inspect Element" - tried to find the web console in the context of the Element Inspector, without success Actual results: Didn´t find a way to open the web console in the element inspector. The only way to open it is going to the default menu, "web developer" and then "web console". Expected results: As a JavaScript Developer / Frontend Engineer and using for years firebug, IE developer tools, Opera Dragonfly, Chrome Web DevTools and Safari DevTools I´m VERY used to check for the web console at the same place as the Element Inspector. I´m only going to change css or check my selected html element, I´m mostly going to open the web console. I need it there, it´s my usuall process. For the sake of web developers love, please don´t hide it on the top menu. Other alternative: show the Developer Bar by default in the context menu (right click) instead of or together with element inspector. Thanks.
Component: Untriaged → Developer Tools: Console
Thanks for the bug report. We do not intend to add the Web Console as an option in the context menu. However, in Firefox 19 (or 20?) we are adding the developers toolbox, which makes it easier to switch to the Web Console, after you click "Inspect element".
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Thanks, Mihai. I´ve got the Nightly version (22) and this is exactly I was expecting. I know it´s not made after my ticket but for the records I´m sure it´s not needed to worry for any new feature about I asked. It´s already implemented.
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.