More and more frequently I was getting this for the actual search terms, in quotes or not, to the point where I would Control+F any words just to find none of them existed on the page. It's the reason I switched to dumber search engines.
I've assumed the "fast path" is to search for "phrases with similar meaning", rather than actual words. But that really destroys technical searches.
If you haven't read our post, I'd encourage doing do. Quotes do work to find the exact terms specified. But control-F won't locate some of the terms we find when fully rendering a doc -- that's why the list explains using developer tools to search if control-F comes up with nothing.
It might be useful to offer people a way to search for content that is rendered in the page, rather than content that is only visible in developer tools.
The content is rendered on the page. For example, say someone has an email sign-up box. When the page renders, the box appears and it might list all the countries in the world, so that you can pick your country from the list. All those countries are rendered, available if you use the box. But if you ctrl-f search, you might not see that text even though it did render. Real case I looked into which prompted the tip of using developer tools.
More and more frequently I was getting this for the actual search terms, in quotes or not, to the point where I would Control+F any words just to find none of them existed on the page. It's the reason I switched to dumber search engines.
I've assumed the "fast path" is to search for "phrases with similar meaning", rather than actual words. But that really destroys technical searches.