Closed Bug 224654 Opened 21 years ago Closed 21 years ago

"Edit, Find in Page" dialog does not display

Categories

(Camino Graveyard :: General, defect)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
Camino0.8

People

(Reporter: chris, Assigned: mikepinkerton)

References

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6a) Gecko/20031103 Camino/0.7+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6a) Gecko/20031103 Camino/0.7+ Selecting the 'Find' feature, either through the edit menu, or the command-F keyboard shortcut, does not function. The find dialog does not display. Reproducible: Always Steps to Reproduce: 1. Select 'Find' from the edit menu, or press Command-F 2. 3. Actual Results: Nothing. Expected Results: Find in page dialog appears
Confirmed using the 20031103 NB.
Confirmed using 20031104 NB.
well, bugger.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Camino0.8
Works in build 2003102211
The 20031030 NB is the first build in which this is broken. This issue is probably caused by some problem in a .nib file, Bug 223413?
works fine with my build at home, doesn't work on my build at work. i can't find a pattern. the nib is fine, we're getting into the maincontroller, but the window just doesn't show.
I'll bet somebody a cookie that this comes from landing bug 221845. It would be really really nice if the patch in bug 160771 was reviewed/landed because I'd bet that'd take care of this.
Does this happens to have something to do with type ahead search not working in 2003110513 nightly? For example, type "2003" and it finds nothing in this page.
Ah yeah I forgot to put that in a new bug. Perhaps this solves that to?
using build 2003110513 and probably before, type-ahead searching does work, but only seems to search for text links.. not all text on the page.. so if you search for 'next' it will find those, because they're links with 'next' in the text.. but it doesn't seem to search for actual text on the page.. is this a bug or is there some new setting im' not aware of.. ?
.js files in Camino.app/Contents/MacOS/defaults/pref are readed in order of name: 1.all-chimera.js 2.all.js 3.macprefs.js 4.security-prefs.js all-chimera.js is original setting for Camino and should be readed the last. Please rename all-chimera.js to x-chimera.js and relaunch Camino as a test. Bug of typeaheadfind and auto image resize are fixed this change,maybe. an additon: In Build setting of Camino, universalchardet is "enable" and Camino enable it automatically. line for universalchardet in all-chimera.js is not need. Overrapping setting of universalchardet cause killing this function.
Doing the suggestion of comment #11 (renaming all-chimera.js to x-chimera.js) resolves effectively the typeaheadfind and auto image resize bugs! Build ID: 2003110516 on Panther
fixed. stupid stupid.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
don't beat yourself up pinkerton, you're doing a terrific job working on a great browser.. safari still has a long way to go in terms of features..
Sorry, comment #11 was my mistaken.
*** Bug 225255 has been marked as a duplicate of this bug. ***
Marking verified with the 2003111013 NB.
Status: RESOLVED → VERIFIED
comment #10 seems to be applicable once again (it search link text, instead of all text). Using build 2003111414 and the Camino.app/Contents/MacOS/default/pref file list seems right (with zzCaminoPrefs.js being the last one read).
You need to log in before you can comment on or make changes to this bug.