Omnibar incompatibility
I'm a devotee of the Omnibar extension, which does away with the separate search box and makes the URL bar into a search bar. Unfortunately, when TenFourFox serves up a blank result (to do with some other, Omnibar wipes all the text out of the URL bar. This doesn't happen with other builds of Firefox, and I'd really like to be able to use Omnibar in TenFourFox
Firefox builds I have tried to reproduce this bug in:
AuroraFox: Not Present Firefox Aurora (MacIntel): Not Present
TenFourFox7450: Present TenFourFoxIntel: Present Firefox ESR
(MacIntel): Not Present
Thanks in advance for your time and attention, I realize that this bug probably only affects a small number of users (me), but it could have effects on some other extensions that depend in some measure on search results.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Cameron Kaiser on Jan 31, 2013 @ 03:19 PM
Way back in the 4.0 betas I had to add a tweak to how the awesomebar works due to a glitch in 10.4 (issue 21: https://code.google.com/p/tenfourfox/issues/detail?id=21 ). If this wasn't installed, the awesomebar would not only have no suggestions, but would stop suggesting entirely. It makes sense that Intel TenFourFox would have the same issue, because it also has the same kludge for 10.4. Since AuroraFox and Firefox are 10.5/10.6, they don't need it, of course.
I suspect this kludge is interfering with Omnibar, but a screenshot would be helpful to confirm, since I know what the behaviour of the workaround is.
It's probably worth checking to see if the code can be removed now that we are on a later compiler and there are changes to the browser core, but this isn't something I would do in 17, since it may have other knockon compatibility effects and this addon is the only report I've heard of a conflict. The earliest I would try this is 20. Note that if it turns out the bug my kludge fixes is still there, there will be no way to fix this issue unless a different workaround becomes apparent, since having the awesomebar fail to suggest is not shippable.
Anyway, let me see what you're seeing so I can be sure my theory is correct.