Press ctrl-f twice.
https://www.tenforums.com/tutorials/120679-enable-disable-qu...
1. It disappears after a few seconds.
2. It has no "next/previous/highlight all" etc. buttons (it still have these features, just no clickable buttons)
It still makes no sense to me.
I guess maybe a small portion of people would find the auto-disappearing thing useful, even though in normal Ctrl+F all you need to do is pressing Esc.
But the second "feature" totally baffles me. It's not like Ctrl+F is some expensive GUI to launch, why would I want to not have these buttons? Even if you don't need them at all (I don't), you can simply not click them, there is no downside by having them.
It's quite nice for keyboard-only web navigation.
It's ' to trigger quick find in links only mode.
Enter never goes to the next result though, so I am not sure if that is just something different between his setup and mine. I have to use F3 to go to the next result.
Sorry if that wasn't clear. (English is not my first language)
Page Info -> Permissions -> Override Keyboard Shortcuts
You're not the first one to point it out. Please join github.com/mdn/yari to raise your voice. It's an Open Source project after all.
> They should have just had the search field focused automatically
Why? There's a lot of JS to load to make that work. If you never need to do a search (e.g. from a Google search) it would be a potential waste.
> Also, I'm confused, I thought https://mdn.dev/ was the new thing because Mozilla was stepping back from MDN. Is it a fork?
That domain is just an alias we don't currently use. It's still the old MDN from Mozilla. No fork.
Confused by what this comment is meant to say exactly, but just in case its not known already, seems this situation is what the autofocus attribute is for @ https://developer.mozilla.org/en-US/docs/Web/HTML/Global_att..., no JS needed
No, this would be extremely wrong: it’d open on-screen keyboards automatically on platforms that use them, mess with screen readers by dropping them in the search box rather than at the head of the page, and break keyboard functionality, most significantly things like arrow keys and Space for in-page navigation.
The autofocus attribute sometimes seems like a good idea, but it’s actually almost never desirable.
It seems to me that mdn.dev is intended to be the future home of MDN web docs since it is collaborative now, and no longer exclusively managed by Mozilla. But they haven't actually made the transition yet, as any link on mdn.dev points back to the old (current) site at developer.mozilla.org
This is one of the two comments on the article (the other being the rationale as a response for why they used the '/' key to do that behavior.)
> They should have just had the search field auto-focused automatically but that would have done away with their "clever" hack to lazy-load the DB containing every page name.
this would steal away the focus and is not good for accessibility (unless you're building a search engine)
They should have just had the search field focused automatically but that would have done away with their "clever" hack to lazy-load the DB containing every page name.
Also, I'm confused, I thought https://mdn.dev/ was the new thing because Mozilla was stepping back from MDN. Is it a fork? They both carry Mozilla logos, so what's going on there?