Closed Bug 49944 Opened 24 years ago Closed 7 years ago

XUL directory viewer doesn't color visited links

Categories

(Core Graveyard :: History: Global, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED INVALID
mozilla1.2alpha

People

(Reporter: levon, Assigned: bbaetz)

References

Details

(Whiteboard: [xul dirviewer])

Visit a URL such as file:///home/mydir/ to get a directory listing.
Then click on a file to read it, so the URL might be
file:///home/mydir/file.html

Now go back to the directory listing; the file is not coloured VLINK. You cannot
distinguish between visited and unvisited local files. This is a crucial
showstopper for me; I can't leave Netscape behind until this facility is
available ...
*** Bug 50303 has been marked as a duplicate of this bug. ***
dup of bug 48578?
(visited links don´t change color after opening in new window)
This not a dupe of 48578 ... it only occurs for directory listings. Rather it
seems it is a missing feature ...
setting bug status to New
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is global history and probbaly needs work in docshell.
Assignee: radha → rjc
this is a combination of global history and the directory viewer...

Here's what needs to happen:
- make sure that the directory viewer includes global history in it's datasources
- global history needs to answer RDF on whether or not a URL has been visited
- we need styles in the directory viewer to reflect this into the UI
Assignee: rjc → alecf
Priority: P3 → P2
Target Milestone: --- → mozilla1.0
nav triage team: not a beta stopper. 
Keywords: nsbeta1-
Status: NEW → ASSIGNED
Component: History: Session → History: Global
adding 4xp keyword
Keywords: 4xp
resummarizing to reflect what's really going on.
Summary: file URLs are not coloured as visited → directory viewer doesn't color visited links
nav triage: moving to mozilla1.2
Target Milestone: mozilla1.0 → mozilla1.2
This is a regression from Netscape 4.x, any chance of its target milestone being
moved up?  I still have to use Netscape to navigate HTML trees I work with
because of the lack of visibility to where I've visited.  Some of these
directories have 500 files in them with many files having similar names so the
ability to see what I've looked and what I haven't is invaluable.  I use Mozilla
for EVERYTHING except this now, though I'm still forced to use Mozilla for it
occasionally if I view a complex page that Netscape 4.x cannot properly render.
 I don't know how many people notice or care about this, but I think that as a
regression from Netscape 4.x its milestone should be reconsidered.
argh.. take two at reassigning history bugs to new owner
Assignee: alecf → blakeross
Status: ASSIGNED → NEW
Target Milestone: mozilla1.2 → ---
-->bbaetz
Assignee: blakeross → bbaetz
This is teh xul viewer, right? file will be moved to the html view RSN - see bug
102812.

When I rewrite the xul viewer I'll look at this, though.
Summary: directory viewer doesn't color visited links → XUL directory viewer doesn't color visited links
-> 0.9.7 for <outliner> rewrite, although I don't know if this is possible
Target Milestone: --- → mozilla0.9.7
I'm guessing that the easiest way to do this would be for outliner to support
:visited, somehow.

Less important since html is the default, though

blake?

-> 0.9.9
Target Milestone: mozilla0.9.7 → mozilla0.9.9
OK, moving all XUL dirviewer bugs to post 1.0. I don't want to be doing this,
but there are only so many hours in the day. These will be taken earlier if
someone submits a patch, or I find time.
Target Milestone: mozilla0.9.9 → mozilla1.0.1
Following the roadmap, 1.0.1 is a maintenance release, so pushing off features
(xul direviewer) to 1.1
Target Milestone: mozilla1.0.1 → mozilla1.1
xul dirviewer bugs -> 1.2. I have no time..
Target Milestone: mozilla1.1alpha → mozilla1.2alpha
Whiteboard: [xul dirviewer]
QA Contact: cmaximus → history.global
Both handling "visited link" and history have changed greatly. WFM.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.