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