User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36

Steps to reproduce:

d

Actual results:

d

Expected results:

d

https://github.com/RoryCombe/FaviconBar or https://www.midwinter-dg.com/software/search-all.html

this means reenable multiple bar support, like safari 12 or previous versions, so that developers can use it.

Steps to reproduce:
d
Actual results:
d
Expected results:
d

Please always fill out all fields, instead of letting other people spend time guessing what you mean or did.

Please always provide a use case. You are requesting that someone else spends time to implement your solution and then maintain and test that additional code for many years to come, but you do not explain which actual underlying problem your proposed solution would solve. Please see https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem#answer-66378

there is nothing to say, because the screenshot says all. you need to implement multiple extension bar (in safari 11 style or palemoon) or like i wrote to chrome too
https://bugs.chromium.org/p/chromium/issues/detail?id=1130322&hotlist_id=9983&sort=%20rank%20-ID. it's all here. is not the first time you write me the same things again and again for basic features (like activate sync and you get verfication code --> then you say please provide step by step). is like if now i need to provide step by step to eat a banana: 1) go to supermark, 2) take a banana 3) pay the banana, 4) ... which is simply ridicoulus. your are developers, so you should already know such things. if something is more complex, then i write without problem step by step, but not for such basic functions where a step by step is not need at all.

See my previous comment. This lacks a use case.

your are developers, so you should already know such things.

No, we can neither read your mind, nor will developers spend time and efforts on stuff if nobody explains why that stuff is wanted.
Nor am I a developer.

what should i write: goal add ability that developers can create specific extension bar is to use an extension bar only for such extension, and i already provided you examples of 2 safari extension, and you see the usage in palemoon too. In palemoon the ability to add extension-specific bar are huge limited, we can just simply add new bar and then move extension to other bar. so palemoon doesn't support (or at least devs doesn't offer) a specific dev extension bar. on chrome we can do it for example with https://chrome.google.com/webstore/detail/searchbar/fjefgkhmchopegjeicnblodnidbammed on the button, but is not a real alternative to what we can do in safari style.

Hi,

I will move this enhancement over to a component so developers can take a look over it. If this is not the correct component please feel free to change it to an appropriate one.

Thanks for your report.