Closed Bug 141907 Opened 23 years ago Closed 15 years ago

place "home page" setting in bookmarks file

Categories

(SeaMonkey :: Bookmarks & History, enhancement)

Product:
SeaMonkey
Component:
Bookmarks & History
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: alliancemillsoft, Unassigned)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc1) Gecko/20020417 BuildID: 2002041711 Right now there are people that want to open a group as a home page and people that want to have Mozilla open the last used group on startup. All this in addition to the usual home page settings. I propose that we make the home page setting a special folder in the bookmarks file. That folder could contain a group or a regular link. It would also have the advantage of keeping the home page settings in the bookmarks file so that when you move bookmarks from one machine to another, the home page setting follows. So what about the users that want Mozilla to to open to it's last used group? Once they select that option in preferences, Maybe a prompt during shutdown that asked them if they want to preserve this group for their next startup. On "YES" the would be written to the "home" folder. Reproducible: Always Steps to Reproduce: 1. go to setup your home page URL. 2. try to enter a group into the URL box. 3. notice that you cannot do it. Actual Results: user angst. Expected Results: see summary It's really distrurbing that "enhancement" is listed even below "trival" in the severity list. Mozilla has only one chance to get tabs right. We need a method to use groups for home pages. We mioght need a method a to save a group for loading on next startup. Users have already asked for these things and groups have only recently been released. As users discover what they can do with groups they will, most surely, push to have groups as home pages. This change would build future functionality into the system and provide a method of the home page supporting whatever future enhancements arise over time.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I disagree. IMHO, the other two requests you mentioned should be enough. Is the ability to move your home page with your bookmarks really that important? This seems like bloat and unneeded special casing, and ATM would wreak havok, since a lot of people's bookmarks already contain their home page(s). The current implementation has problems dealing with multiple instances of the same bookmark. Bookmark groups would only multiply this potential conflict.
That's fine. It's the features that are important. This is just an idea for implementing these ideas, along with any new bookmarks ideas that appear at a later date. Tabbing really changes the ways that users will be thinking about bookmarks, and home pages, and downstream I can envision where someone will create a linking method that could take advantage of tabs. Can you imagine clicking a link on a web page and having it open up a series of pages in tabs? If tabs are sucessful, and they will be, these kinds of things are coming. By embedding the home page into the bookmarks file we're creating a method that would accept any new ideas in bookmarks and links.
With this type of layout it's possible that we could have Mozilla startup using multiple windows and groups in each window. Wouldn't that be something? Open Mozilla. Three windows open, with 5 tabs per window, the first window gets primary focus and thus the first tab in that window loads first. Other tabs load in background, then other windows load in background. In only a minute or two you've checked 15 daily sites that you monitor. Perhaps this could be achieved by having a "home page" folder (or maybe call it startup). Within that folder you would have a series of bookmark groups. Each group would open a new window. Of course you could also have a series of single bookmarks in the folder. Each bookmark would get it's own window. Another idea would be to have a separate sub folder (perhaps callled "new window") for a page to open in a new window. Now Mozilla always uses the home page, which is frustrating for a lot of users. If that sub folder were blank it would open a new window without a page. Otherwise it would load whatever is in the "new window" sub folder. The bookmarks file already a propietary folder that we use for the personal toolbar, so users are used to having special sections in the bookmarks folder. Placing the home page into the bookmarks simply extends this practice and solves the new problems of supporting groups. John Whitling
I don't see the point of having a home page "folder", or do you want the Home button to open new windows for each bookmark/group in the home "folder"? Just nominating a bookmark as your home page would seem sufficient to me.
The point is that bookmarks are changing. With the advent of tabs we now have bookmark groups. In the future we might also have another type of bookmark as well. If we use a folder in the bookmarks file (such as the personal toolbar folder is now used), the tradional home page setting can adapt any changes in bookmarks without further reengineering. 1. Home page can be a bookmark group. There are lots of requests for this already 2. Multiple icons in the home folder would open additional windows on startup 3. When you open a new window you can define a different page load or no load at all via a "new window" subfolder 4. Your home page settings would travel with the bookmarks file 5. Future bookmark changes would automatically be supported Don't these sound like meaningful enhancements?
A great example of "outside of the box" thinking. Bravo breezymozilla!! Though I'm a bit hesitant on point 3 of comment 5, the rest of your suggestion is logical and intuitive.
Wow! Thanks for the heady compliment! For clarification, the issue that you mention (Point 3 in comment 5) relates to opening a new window when Mozilla is already active. With the option of having a quite extensive "home page" setting (multiple tabs in multiple windows), you would most naturally want a new window to open without loading a possible series of windows with tabs of home pages.
Love it. CC:ing myself
Saving browser state like Opera does is really neat. I often find myself bookmarking every open window before logging off and not bothering to check all those bookmarks later. The only downside I found using Opera 5 is that it tended to hang when trying to load a lot of pages at once.
The piece of this enhancement I've found myself wanting several times is to have all tabs restored when I have "Last Page Visited" selected on startup. The rest sounds kindof neat, but I don't have enough experience with the referenced features to really comment. I'll definitely watch this "bug"...
This would prevent Mozilla from loading the home page before loading the bookmarks file. I don't think that's a good idea.
Regarding Comment #11: Why is it a problem to load the bookmarks file first and then the homepage(s)? Does it take so long to load bookmarks? Is there another downside when you load bookmarks at first? IMO even if it takes 2 secs longer to load the homepage it wouldn't be problem. However if you think that loading the homepage fast is important you may think about ("OFF-BUG", new enhancement) caching the homepage. So when Moz starts it will at first display the locally-cached homepage (immediately) and then a new version of it from the internet.
I'm not at all sure that it would take long to load the bookmarks file. My bookmarks file, after probably 10 yrs of internet use, is about 133 kb. How long does that take to load? I imagine that quick start would easily load the bookmarks file into memory, if it doesn't now. In addition, there is nothing to say that the bookmarks file has to be the "final" location of the home page settings. The bookmarks file could be just the user interface. From a programming point of view it might be fitting for the home page settings in the bookmark to be stored in a registry or internal location. This might also suport the option to restart Mozilla with last page settings. I'm not trying to complicate this, but at the minimum we need to rethink home pages to support tabs. We ought to investigate all our options to get maximum benefit for the Mozilla project.
Shouldn't this be marked as blocking bug #118835?
> Shouldn't this be marked as blocking bug 118835? If this bug is marked FIXED then that one should be too. Although, now that I say that, if this one should actually be marked WONTFIX, for whatever reason, that *wouldn't* mean that bug 118835 should also be marked WONTFIX. It's only a positive dependency, not a negative one. I'd lean towards not marking it as a blocker on logical grounds, but I'm not familiar enough with Bugzilla rules to say for sure.
Just to inform anyone on this list that is not already aware ... this bug hasn't had any activity BUT the Multizilla project is worth looking into if you're looking for some of the advanced tab methods that were discussed in this bug. Check out the project at http://multizilla.mozdev.org/index.html
Also, FYI. Bug 118835 has been fixed. Which means that you can now set a tab group as your home page - addressing comment 13 among others.
Product: Browser → Seamonkey
Assignee: bugs → nobody
QA Contact: claudius → bookmarks
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.