communicator 4.x does this --but then again ftp pages there were displayed as html. in mozilla we should able to find strings/etc. while viewing an ftp listing. when the ftp listing uses the outliner view, we should be able to find stuff there using the same mechanism by which one would search the Bookmarks. 1. go to the above url. 2. bring up the Find on Page dialog. 3. enter a string, say "2001-03-11" [without the quotes]. 4. hit Find. result: get a dialog saying that the text cannot be found. expected: should find a directory whose name contains 2001-03-11.

nominating for beta1 and catfood --this is particularly helpful if the listing is long, such as the mozilla nightly build directory. :) [note: this is not applicable if the ftp listing is displayed as html, ie, http://ftp.mozilla.org/pub/mozilla/nightly/]

should this depend on 73509? Will it "just work" once that happens?

heh, i was just thinking about the file:/// view [at least for directory listings], too. so, methinks this would depend on that bug. thanks, bradley!

nav pretriage: Nice to have, but don't think we have time for this. Marking nsbeta1-

This should just work now that we're using HTML listings.

:-) nice. Well, the directory viewer still exists but so I will change the summary and punt it to the future bucket.

sairuh: could you verify if this works and if so mark it as worksforme.

yup, sure do. :)

reopening, and retitling - we use the html directory viewer by default now, but the XUL one still exists, and may be turned back on if someone converts it to <outliner>, and its fast enough.

marking p4

mass moving open bugs pertaining to find in page/frame to pmac@netscape.com as qa contact. to find all bugspam pertaining to this, set your search string to "AppleSpongeCakeWithCaramelFrosting".

-> default assignee

->bbaetz

xul dirviewer -> 1.1

xul dirviewer bugs -> 1.2. I have no time..

this is a generic xul problem, i guess we need an nsIFind impl, inspector (cc:hewiit) has the ability to do dom based (cc:sicking) searches (cc:kin) any suggestions?

If it's a DOM tree, the new nsIFind api and, perhaps, current implementation should be able to handle it. Cc akkana.

I'm not sure what the XUL directory viewer tree looks like. Does it use text nodes? If so, the current implementation should just work. If searching in nodes other than text nodes is needed, then the implementation would have to be extended. I'm probably going to be extending nsIFind to search in buttons and image alt text anyway, for accessibility reasons (bug 158757); we're not sure yet how that should be reflected in the API, since we want it not to happen all the time. Flags for various modes of operation? (Sigh) Kin, any thoughts?

I see "about:config" in this bug's status whiteboard. Should bug 103911 depend on this one?

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

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

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

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

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

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