Thanks for taking the time to file feedback! We can look into optimizing these use cases in MD Settings.

Note that the old Search engines section was not ideal for everyone because it relied on hover to see the edit/remove controls, so we are trying to make those more accessible with the 3-dot menu.

>Note that the old Search engines section was not ideal for everyone because it relied on hover to see the edit/remove controls, 

Sounds like something taken from a thin air. Hover was used for ~20 years on desktop platforms successfully and suddenly it's a problem? No, because it's a problem specific to touchscreen UX. Whereas for desktop users with a mouse or other pointing device relying on hover has always been the most natural thing to access/showcase/provide additional functionality in an obvious, yet noninvasive fashion: one sees something one wants to alter and one hovers/clicks/doubleclicks/rightclicks it.

>so we are trying to make those more accessible with the 3-dot menu

1. it's definitely not more obvious/accessible for nonsavvy users as they won't notice small extra icons for the exact reason they're nonsavvy
2. it's definitely less accessible for all users since two additional clicks are required using an obscure icon
3. it's nonstandard and non-obvious on desktop platforms

I'm worried by this sudden decision to cripple desktop Chrome's UI/UX and make it behave in nonstandard (for a desktop app), hindered fashion trying to embed the severely limited touchscreen UX. It's like Orwell's 1984 with meaning of words reversed: "obscure is accessible!"

My rant above is about the editing functionality, previously available immediately on hover. As for other actions, I surely can agree with #2: as soon as non-geeks started to be the absolute majority of computer users, rightclick and hover are considered obscure.

Eureka!

Simply show the edit card/dialog on single click on the item with all the action buttons inside the dialog (Save, Cancel, Remove, Set as default). This would be an obvious and intuitively accessible solution.

Currently the most intuitive gesture - singleclick on an item - does nothing meaningful. And even worse, it paints the row gray for no reason implying it might do something, but nothing actually changes.

@dbeam thinks this UI could be modeled after the new cookies UI in content settings.

honestly, I think we should make menus trigger on mousedown and allow selection on mouse up after a certain number of ms (like native context menus or gmail)

or something else that Tom wants to do (that is silly)

I am repurposing this bug to track any future MD Settings search engines UI improvements (see deduped bugs).

 Issue 675331  has been merged into this issue.

 Issue 673032  has been merged into this issue.

Clearing my ownership of P3 UI>Settings bugs. Feel free to re-assign once triaging is complete.