Search field is missing

[marcela...@gmail.com]

With the new version of Chrome 22.0.1229.79 m the developer tools is not showing up the search field. Screenshot:  http://screencast.com/t/DwFxDGs2E

I've searched on settings a way to bring it back but I haven't found anything. Maybe now it's like an optional feature...

Please advice :/

[Nikita Vasilyev]

Ctrl + F

[marcela...@gmail.com]

yes i do know the ctrl f brings up a search field but I don't want that, before there was a search field 'Search Element' which was located in the upper right corner of the toolbox. That's the one I want and its not showing up.

[PhistucK]

Within the Developer Tools, pressing Ctrl + F is the way to bring up that search field now. I also think it is weird.

☆PhistucK

[kam...@complex.com]

Command+F on Mac. It works but it is annoying. I hope they will bring back the regular search box soon. It is not like it was occupying a space that is now used for something more important...

[pbie...@gmail.com]

I think this new search field sucks - it doesn't even show the number of matches. 

[Vsevolod Vlasov]

Thank you for your report. 

I have filed https://code.google.com/p/chromium/issues/detail?id=153753 for the number of matches issue.

On Tue, Oct 2, 2012 at 8:47 PM, <pbie...@gmail.com> wrote:

I think this new search field sucks - it doesn't even show the number of matches. 

--
Thank you,

Vsevolod Vlasov (vse...@google.com)

[des...@digitup.se]

I have the same issue and I really think it is annoying. Why did they remove the search box in the first place? it should have been better to have it optional feature. 

[r.j...@gmail.com]

OMG that is indeed annoying. Why should I press Ctrl F for something which should be there always! damn it.

[Pavel Feldman]

You should not need to undock anything - if you have focus in the devtools, it'll just work. We'd like to have more real estate in the toolbar for the dock-to-right mode where toolbar elements overflow otherwise. Most of the IDEs / tools / browsers have shortcut-controlled search capabilities, so we hope it works well for the users. We'll try to make it more discoverable though.

Thank you for your feedback

Pavel

On Wed, Oct 10, 2012 at 7:29 PM, <jay.r...@gmail.com> wrote:

You have to undock the developer window from the main browser in order for ctrl-f to bring up the search...it really is a pain

[Zachary “Gamer_Z.” Yaro]

If that is the reason, could you maybe consider showing the search box when the devtools are wide enough and then hiding it when they get narrower?

—Zachary “Gamer_Z.” Yaro

[zikr...@gmail.com]

I'm really frustrated by this change as well.

A few more bugs for the way it works now.

1. If you are searching for string, and need to perform the same task on multiple page, say in the network tab for a file that's consistent from page to page, and you have a search term entered that will identify that file when you move to a new url, your search term will still be there, with the counts the same as the search on the previous page. It does not automatically re-search the current content like it used to. You need to delete your term and search again.

2. Pressing ctrl f after the console is open will often times open the find for the standard browser window, not the console, it's difficult to tell if the console is focused.

[ma...@upcounsel.com]

Why the hell was this changed?! 

I can't think of a single good reason.

On Friday, September 28, 2012 11:39:21 AM UTC-7, (unknown) wrote:

[zikr...@gmail.com]

I had to go back to FF, it was so frustrating.

[cjf...@gmail.com]

have to agree - its terrible - using FF now also 

This used to work also but no longer :

  search term and press enter, code jumps to first match

  click to add breakpoint, focus would remain on search term so i could press enter again to find my next match and add another breakpoint, 

  now, when i add breakpoint, focus switces to the code, pressing enter deletes the matched text from the code editor , code alteration means the runtime debugger stops functioning, have to re-open it , start again....

.. so frustrating... please put permanent search box back or add config option to permanently keep it.

[lilyla...@gmail.com]

Yes it's annoying, I thought it was me disabling it by accident....add it back...don't want to have to use FF again...

[smooth...@gmail.com]

Guys our application has 20,000 lines of javascript with many dynamically generated classnames and id's (ie I can't grep the code). The *only* way I can find certain things is the search bar; I use it all the time and what you have (arbitrarily) done is unnecessarily frustrating to use.

I seriously cannot see what you have gained by eliminating it. It was clear and beautifully easy to use. How is 'ctrl + shift + f' even remotely close to using the search bar? Who can possibly say that that is user friendly? To be honest the debugging interface in general has gone backwards and not forwards in the last few months - the sources tab is an unnecessary and unfriendly mess with, sometimes, my own sources not even showing up.

Could you not, at the very least, make the search bar an option? What possible difference is it going to make?

James Drummond

ps. Ctrl + shift + f does not even work. Let alone that it does not show how many matches there are and seamlessly navigate to them but, as far as I can tell, it just plain doesn't work.

pps. Ohhh... I get it! It does work but it doesn't show anything if you've got the console window open. You have to close the console window then press ctrl + shift + f *again* and there are your results!!

Seriously what a joke.

[Pavel Feldman]

Did you try Ctrl+F?

[smooth...@gmail.com]

Thanks for your reply.

ctrl + f searches the current document in sort of the same way that the old search worked (although it's a lot easier to just focus on an input box than pressing 'ctrl + f' - just saying).

But, like I say, I search thousands of lines of code from many files.

You had it right before guys. It just worked and worked well.

Cheers, James. 

On Friday, 2 November 2012 11:50:54 UTC, pfeldman wrote:

Did you try Ctrl+F?

[Pavel Feldman]

Wait, the only thing that has changed was that we freed up some space in the toolbar and now we show the search field upon Ctrl+F. No semantic changes took place, just the field being hidden by default.

[Pavel Feldman]

Going back to steps, the only change that was made was that Ctrl+F became necessary for search field to show up. If you are seeing anything else, please let us know. The new behavior matches all the IDEs and editors, pretty much all the browsers do it that way. The reasons behind the change were that we saw more and more people adopting the dock-to-right mode and having the search field visible at all times was making all of them miserable (Console tab was getting off the screen). Furthermore, we are currently working on another visual toolbar redesign that makes search field there simply impossible due to lack of space.

Not accompanying the change with the announcement was a clear oversight from our side. We are fixing it now. From the other hand, flexibility like that makes us iterate more quickly and bring even more good features to you.

Regards

Pavel

[Vsevolod Vlasov]

No feedback, no number of matches, no nothing. I'm trying this whilst I type and actually I can't even get it to work. I'm pressing enter, clicking the search icon and nothing is happening.

This looks like a regression! Could you please provide more details? On which panel do you experience such a behavior? Could you please provide an example url, your browser version and a screenshot if possible?

 

Step 4: See your results. I can't actually get this far at the moment.

Again, please provide some more details! I'll be happy to fix this. 

 

I just think that every developer needs to navigate their code all the time and the quickest way to do that is start typing a keyword - word to search for in the code. You've introduced at least two new steps before anyone can do that and the results are not nearly as good as they were.

The bugs that you have pointed out seem very frustrating to me, we should definitely fix them before making any new changes in the ui.

[Marcela F.]

I totally get you James, that's the reason of my complain. Ctrl+F does NOT work the same way the old search box did. Could you please add the functionality that shows you the number of matches at least?

 

There is an empty space where the old search was so I dont see the point in making the 'new' search optional because when you bring it up it takes space.

[sam.w....@gmail.com]

I am running Version 23.0.1271.64 m and some of the functionality has been restored. You can see number of matches and use the arrows to cycle through them. However I still see some usability issues with this. 

One of the things I like about Chrome is the efficient use of space and this latest change does not seem to follow suit. The old search box fit nicely on the bar which is now just blank area. The new search creates a whole new bar which limits your view of code.

When I am working I frequently interact with the main page and then check things in the developer panel. If the developer panel does not have focus Ctrl + f brings up the page search and not the search in the developer panel. Causing the users to click into the search box forces focus into the right area, where as pushing Ctrl + f will bring up the wrong search box if the web page has focus.

Ctrl +f is a universal search command however the old bar allowed me to work faster. Could you have focus given to the old search bar from that command? That way you preserve Ctrl + f functionality but have a visible search bar.

[mrb...@gmail.com]

ctrl-f doesn't even work properly, tried it for the net console, it doesn't match half of the stuff it's supposed to

[Vsevolod Vlasov]

Could you please provide some more details: a specific url and reproduction scenario, your browser version. Otherwise it is hard to identify the problem.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Bart Bobrowski]

here's an example...

chrome: Version 24.0.1312.56 m on Win7, & 24.0.1312.56, mac osx 10.8.2

open dev tools, goto the network tab, then load https://www.google.ca/

now go ctrl-f, type in: gstatic

it returns no matches, however if you manually search the rows you
will see a request has been made to ssl.gstatic.com

let me know if you are able to reproduce the bug

-bart

[Vsevolod Vlasov]

This is a bug (name and host shown in network panel and used for search were inconsistent) that was fixed starting from Chrome 25. You can try using Chrome Beta / Chrome Dev / Chrome Canary versions as a workaround right now.

[levide...@gmail.com]

I THOGHT U CANT DO BETTER THEN CHROM, WELL NOW WE CAN........BACK TO FIREFOX....GOOGLE THIS TIME U LOST

[jillia...@gmail.com]

This is driving me crazy. When I type cmd-f in my mac it just starts searching the actual web page (even though I am focused in dev tools).  When I select scripts and hit cmd-opt-f, it acts like the dev tools isn't even open and starts doing the default "?" (enter query) up in the address bar. Can anyone tell me why I can't even search at all in dev tools anymore like you all can with the shortcuts?

Thanks.

[Vsevolod Vlasov]

Could you please provide more details: your OS, browser version, reproduction scenario (with site URL if possible)

--

[Vsevolod Vlasov]

Could you please provide more details: your OS, browser version, reproduction scenario (with site URL if possible)

--

[usj...@gmail.com]

Now for 2 weeks the Search box inside developer tools (that allowed me to search all the css, js and html at once) is gone. When I hit CTRL F inside the Resources Tab , it used to pop up , now nothing happens. I can still search inside the Elements tab (the live html) but who needs that, the value before was that I could search for something and instantly see if its located in any of the files and get a line number. Why in the world would you remove such awesome functionality?!?!

 I am using latest Chrome Version 32.0.1700.41 m Aura on Windows 7 pro , 64bi desktop. 

Thank you in advance for your help.

Nick

[John J Barton]

Try your search in the Sources panel. Is it sufficient?

jjb

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/ac337d90-b366-422c-8900-885ac2d6a94c%40googlegroups.com.

[Vsevolod Vlasov]

Try Ctrl+Shift+F (Cmd+Option+F on Mac) to "Search across all sources".

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

[Jillian Green]

I figured out why mine disappeared. I had switched my keyboard layout to Dvorak while keeping Qwerty shortcuts. Turns out this part of the dev tools didn’t respect the Qwerty shortcuts in this scenario, but would accept the Dvorak one instead. It’s funny because the rest of Chrome doesn’t seem to have any issue respecting these.

You received this message because you are subscribed to a topic in the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-chrome-developer-tools/38xxnruDG40/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CAB6O%2BxaWXu3Wtc3KByh-FytYNFkoY1Dk_VhWyFRmpuGbuYgm7Q%40mail.gmail.com.

[mukti pukti]

Googling for "chrome search all files" brings up this:

search across all your scripts with support for regular expressions and case sensitive search: 

 Ctrl + Shift + F ( Cmd + Option + F on mac) 

[Kevin Dollabillz]

I whole whole-hardheartedly agree Google has RUINED Developer Tools. Stop telling people to just do control+f people that does Not bring back the Old search it brings in the new Garbage search that doesn't find jack squat.

I had to downgrade my chrome last night to get the old search back I suggest  u do the same until Google stops ruing stuff

I got it here

https://www.slimjet.com/chrome/google-chrome-old-version.php

64 bit -      66.0.3359.181                  48.58 MB                     2018-05-16

[PhistucK]

What are you talking about? It cannot be the same issue from three years ago if you offer Chrome 66 as an alternative...

☆PhistucK

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

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/eb54684e-76c0-4f22-8f13-3621aa9ab18e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kevin Dollabillz]

Well gdam I didnt even notice the Post Date i just clicked on the first result in Googlez about the search field being missing haha

Anyway the downgrade fixed My issue with it being missing.

[PhistucK]

Can you elaborate? Which search box? Care to provide a screenshot?

☆PhistucK

--

You received this message because you are subscribed to the Google Groups "Chrome DevTools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/1eff9d63-a485-4f87-b334-80e3afec831e%40googlegroups.com.

[Kevin Dollabillz]

Yea for sure here is the search box that was Missing

https://snag.gy/79ohZs.jpg

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CABc02_%2BTQJ9ky1KfLd2BwkxXQVu7Q1fRLfHODG6oz3WPLQ7PpA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Kevin Dollabillz

CMS Global

http://simplecloud.ru

dolla...@mail.ru

[PhistucK]

And in which version are you not seeing it? I use Chrome 67 and I see it (as long as the filter button above it is enabled) -

☆PhistucK

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CAKAwmyX77pijDrgp2F4tiPH%3DVqnoqaFrEGxr2wTNGHfOOr%3DsEQ%40mail.gmail.com.

[Kevin Dollabillz]

Whatever version is out Now 2018-07-25  i had just updated it 6 days ago.

I cant tell you exactly as i have downgraded the version to what i posted up above...

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CABc02_Koi3tpGw4paugRTtn6dTs9G8dr%3DE6B2sH1ZXcF1KJfeQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[PhistucK]

Downgrading is a bad idea as older versions have known security vulnerabilities.

Maybe the filter button got back to disabled for some reason and so the search box is missing.

I strongly urge you to update to the latest version, unless you do not care about being hacked easily.

☆PhistucK

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CAKAwmyXw2WsRddsrhyVmHyh8ChARTfCLCKN-Y8NoEwzK9xELTw%40mail.gmail.com.

[Kevin Dollabillz]

Thanks for the advice. I've been and it guy for 21 years I no longer worry about Viruses :)

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CABc02_LkaX2kpVKCbH-3rv9ewFBvuZKjOdXE-kZjsWq7BK1fSA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[PhistucK]

That sounds... Reassuring (sorry, it is totally not).

Anyway, you do need to stay updated in order to develop on/test the version that most users are using (I can only assume you are a developer). If you also do not care about that, then (weird, but) fine.

(But, if you are, as an IT person, keeps your users from updating to the latest version, then you are jeopardizing your users or your entire organization)

Anyway, the right thing to do is to file an issue about problems you are facing. Sometimes those problems are not design decisions/features, but quite simply bugs that only manifest in certain configurations.

☆PhistucK

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CAKAwmyXJ_Cxt2mnei51fqoXY9CkiXhq6uS%3DttCd7zHxP3kxP0Q%40mail.gmail.com.