Closed GoogleCodeExporter closed 9 years ago
Agreed.
The obstacle is that the option to override the New Tab page can only be set in
the extension's manifest.json file, which can not be altered by the extension.
I'll have to release a whole new extension. Think I'll call it "Fauxbar Lite".
Will narrow its scope to just Omnibox integration, and have only a few options
like limiting URL length in results, hiding "http://", using custom frecency
scoring if desired, etc.
But will chop out everything else, like adding search engines, thumbnails and
tiles. I don't think there'd be a need to retain the normal Fauxbar page at all.
I'll start on this in the next few days.
Original comment by fauxbar....@gmail.com
on 28 Sep 2011 at 9:58
Original comment by fauxbar....@gmail.com
on 1 Oct 2011 at 7:55
How is Fauxbar Lite going to differ from the Awesome Bar extension seen here:
https://chrome.google.com/webstore/detail/epfjibmdcelinmbfeimnfeeggpebleje ?
If there's not going to be any difference, then would Fauxbar Lite even need to
be created?
Original comment by lilsli...@gmail.com
on 2 Oct 2011 at 9:21
That AwesomeBar extension only searches your bookmarks, doesn't bolden matching
words, doesn't show URLs, probably doesn't use a ranking algorithm, and its
default suggestion doesn't work.
Having tested a stripped-down Fauxbar Lite version a bit, not having a main
Fauxbar page available *at all* is actually quite annoying. Tried it, didn't
like it. I thought it might be the way to go but not anymore.
So, I'll just disable the New Tab overriding from Fauxbar and call it Fauxbar
Lite still, but may change/add a couple of other things to ensure its usability
and setup flow is not hindered.
If Chrome let you choose which URL to use as the New Tab page, it'd be heaps
better. Might suggest this to crbug.com.
I may add an option for Fauxbar Lite to make the New Tab page be "overridden"
(eg when Chrome's New Tab page launches, Fauxbar detects this and tells the tab
to go to Fauxbar's main page), just in case you're going through a browsing
session where you really want your New Tabs to be Fauxbar's temporarility, but
the delay of detecting and updating the tab to Fauxbar's page is a bit slower
this way instead of having it directly enabled in the manifest, so it's not
_that_ ideal. I'll see if it's worth including.
I'll also fix/implement issue #29 (for both Fauxbar and Fauxbar Lite), so you
can right-click on search fields to add search engines (like Chrome lets you do
now). Then, I can remove the blue/orange Fauxbar+ icon from within the Omnibox,
and just have a designated Fauxbar button beside the Omnibox instead, which
would open Fauxbar's main page either in current tab, new tab or new window
(selectable option), and this would also provide easy access to Fauxbar's
options by right-clicking the icon.
Original comment by fauxbar....@gmail.com
on 2 Oct 2011 at 10:24
Fixed in Fauxbar Lite v1.1.1:
https://chrome.google.com/webstore/detail/bfimmnpbjccjihohjkimphfmmebffbmk
Details from the changelog:
- Fauxbar Lite is identical to Fauxbar, except:
- Fauxbar Lite does not replace Chrome's New Tab page.
- Fauxbar Lite has the Alt+D, Ctrl+L and Ctrl+K override options disabled by default.
- Fauxbar and Fauxbar Lite are not meant to be run simultaneously. If both
extensions are installed, when one extension starts, the other will be disabled
automatically.
- Fauxbar and Fauxbar Lite's databases and options are kept separate from each
other; the two are treated as individual extensions. However, options can be
manually exported and imported between the two via Options > Management.
- Future updates to Fauxbar will also be applied to Fauxbar Lite. Version
numbers should remain identical.
Original comment by fauxbar....@gmail.com
on 14 Oct 2011 at 2:32
Original issue reported on code.google.com by
DeathByN...@gmail.com
on 28 Sep 2011 at 8:46