Undesired effects from using bookmarks
nomad —Thu, 09/11/2008 - 22:46
Hi,
A couple of issues from fastdial now using bookmarks to store it's configuration.
First, I have a load of bookmarks that are now blank as I remove the title from the thumbnail. I have these bookmarks with no title dumped in the service I sync to and the Recently Bookmarked folder. At least they stay out of Most Visited and the address bar :)
Maybe the ability to not display the title on a thumbnail by thumbnail basis would be a solution (and the ability to reference bookmark folders outside the Fast Dial folder?)
Note that since the back option dissappeared, I am using thumbnails pointing to chrome:blahblah urls. These folders also have no name, nor any reference to the shortcut when moused over in bookmark manager. I quite like the preview displayed of the previous page (feels a little bit better than the old arrow) and someone asked in another post about the Back option in context menu. That is fine, maybe a small back arrow should be displayed at the top or something.
Second is the display order. I found that one folder was moving the thumbnails around, I guess on date accessed order or something. Setting the folder to Sort by name and dragging the bookmarks seemed to fix this one folder so far.
f 3.0.1 fd 2.8
Online users
There is currently 1 user online.
Active - 15 mins:
Active - 15 mins:
Re: Undesired effects from using bookmarks
Submitted by nomad on Fri, 09/12/2008 - 00:54Ok, another related issue with bookmarks. When adding a new thumbnail from the context menu the page is just dumped into the bookmark list at the end. This means FD no longer uses blank cells for a new thumbnail first and also the new thumbnail can be off the screen as the grid is too small.
The thumbnail is added at root of the FD bookmark folder and no longer recognises which page is open as used to happen in previous version. (Also no longer remembers which page was open last and defaults to the first page)
Lastly I cant seem to drag and drop into a folder, I guess its the chrome addresses stopping this version from recognising its actually a folder, will check js console tomorrow.