From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; SunOS 5.7 sun4u; en-US; m17) Gecko/20000810 BuildID: 2000081017 If a document has no <title>, its history entry in the Go menu is blank. That makes it a bit hart to select. It's also confusing if I want to go e.g. 2 documents back but don't notice that there is a blank history entry in the middle, so I go 3 elements back instead. (It's also blank in Tasks/History, but that's less important since the filename is visible next to it.) Reproducible: Always Steps to Reproduce: 1. Visit the specified URL (or some other without title). 2. Click on the Go button. 3. Click on Tasks/History and sort by last visited. Actual Results: Blank history titles Expected Results: Some component of the URL (the algorithm to pick it doesn't need to be advanced).
I'm sure law's latest checkin fixed this. If not, I will.
Assignee: radha → BlakeR1234
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Solaris → All
Hardware: Sun → All
I'm mostly sure this is a dupe of bug 22174 (the bug law was checking in a fix for)
Mozilla built today from cvs tip on solaris8intel Go history displays the url :-) The window title is useless and therefore the tasks entry is useless, but that's for an enhancement bug (the url should be displayed in both places).
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
what are you trying to say? Your last comment doesn't seem to make sense (we display the url but we should use the url?). AND, this is just a dupe of bug 22174, say why it isn't.
Well, I'm not actually sure that it's an exact dup because that bug dealt with FTP and local file entries in SH, whereas this bug is just *any* html page that has a blank title (<TITLE></TITLE>). However, since Law fixed 22174 by checking to see if the title was empty and then using the URL if it was, that also fixed this bug. I, too, am confused by timeless's comment though.
mass-verifying claudius' Fixed bugs which haven't changed since 2001.12.31. if you think this particular bug is not fixed, please make sure of the following before reopening: a. retest with a *recent* trunk build. b. query bugzilla to see if there's an existing, open bug (new, reopened, assigned) that covers your issue. c. if this does need to be reopened, make sure there are specific steps to reproduce (unless already provided and up-to-date). thanks! [set your search string in mail to "AmbassadorKoshNaranek" to filter out these messages.]
Status: RESOLVED → VERIFIED
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
You need to log in before you can comment on or make changes to this bug.