Operating system
Linux
Version
Version 0.7.9.1 (Official Build, Chromium 143.0.7499.169) Arch Linux (64-bit)
Have you tested that this is not an upstream issue or an issue with your configuration?
Description
Activating a bang trims whitespace around query, breaking bangs in middle of query compared to search engine bangs
How to Reproduce?
- Start typing a search query:
helium
- Add a bang while in the middle of a search:
helium !g
- Activate the bang with Space
- Continue with the query:
browser
Actual behavior
Activating the bang trims the query after removing the bang, deleting the space before between helium and !g leaving you with:
Expected behavior
This is the behavior you get with the same input using search engine bangs like DuckDuckGo: helium !g browser
Additional context
This does not affect usage of bangs in the start or end of the query, since there would be no whitespace to trim or nothing more to add to the query receptively.
P.S. "Have you tested that this is not an upstream issue or an issue with your configuration?" is not applicable here since it's a helium feature (and already tested with an empty profile).
Operating system
Linux
Version
Version 0.7.9.1 (Official Build, Chromium 143.0.7499.169) Arch Linux (64-bit)
Have you tested that this is not an upstream issue or an issue with your configuration?
--user-data-dircommand line argument and it could not be reproduced thereDescription
Activating a bang trims whitespace around query, breaking bangs in middle of query compared to search engine bangs
How to Reproduce?
heliumhelium !gbrowserActual behavior
Activating the bang trims the query after removing the bang, deleting the space before between
heliumand!gleaving you with:Expected behavior
This is the behavior you get with the same input using search engine bangs like DuckDuckGo:
helium !g browserAdditional context
This does not affect usage of bangs in the start or end of the query, since there would be no whitespace to trim or nothing more to add to the query receptively.
P.S. "Have you tested that this is not an upstream issue or an issue with your configuration?" is not applicable here since it's a helium feature (and already tested with an empty profile).