Target Milestone: --- → Future
If home() just re-loads a single page/tab, then the worst you can do is re-load the same page over and over. Memory usage shouldn't grow. If home() re-loads (as it does now) a whole new set of tabs, memory growth can be significant, in principle hanging the browser.... Of course you can kill both with the stop button ... but it was memory consumption I was thinking about. ....
I suggest that window.home does load the first homepage in current tab. Currently it loads the concatenated string (http://www.site1.com|http://www.site2.com), which eventually produces a 404. Tested with firefox 2.0 and following link : http://en-us.www.mozilla.com/en-US/firefox/2.0/whatsnew/ , "go home"
Dupe of bug 343999?
No, it doesn't appear to be a dupe. Under Firefox, a 404 is generated. Under SeaMonkey the original behaviour reported here (just loading the first tab) still happens.
Assignee: jag → nobody
QA Contact: pmac → tabbed-browser
Target Milestone: Future → ---
SM2 doesn't have the option "2. Set this group of tabs as your Home page." any more. WFM
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Menu - Edit - Preferences - Browser - Homepage
You need to log in before you can comment on or make changes to this bug.