306102 - Find in Page - can't enter data in Find Text box after using BBEdit 7.1.4

Status: RESOLVED FIXED

(Camino Graveyard :: General, defect)

Description

[Janet Moe]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050427 Camino/0.8.4
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050427 Camino/0.8.4

After using BBEdit's search function, I am unable to change the text in the
'Find Text' box in the Find in Page function.  The text that shows there is
whatever I last searched for using BBEdit, and if I open BBEdit and change the
search term in that search box, the text in the 'Find Text' box in Camino
Changes.  Even if I quit BBEdit, I can't change the text.  Also, if I've
searched in Camino, then open up BBedit and use the search function there,
whatever I've searched for in Camino shows up in the BBEdit search box.  I'm
using 10.2.8 as my OS.

Reproducible: Sometimes

Steps to Reproduce:
1. Use BBEdit to Search.
2. Search in Camino
3.

Actual Results:  
Unable to enter any text in Camino's Find Text box - text there is what was
searched for with BBEdit.

Expected Results:  
Allowed me to change the text.

Comment 1

[Samuel Sidler (old account; do not CC)]

Seeing the text from another app is part of OS X's global search functions, I
believe.

Can you please try this with a 0.9a2 or a more recent nightly? A lot of bugs
have been fixed since 0.8.4.

Comment 2

[Marnia]

The "find" feature will find words in the rest of the page, but not in the text
box, which is the only place you really need it to search.

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

I think Mike fixed this when he implemented "Use Selection for Find", but my
memory is fuzzy.  At any rate, I have no problem changing the text that the
global find pasteboard enters into Camino's "Find in Page" panel.

Camino 2005091404 (v1.0a1), 10.3.9.

Reporter, please test with Camino 1.0a1 and let us know if the issue still
occurs or is resolved.

Comment 4

[Janet Moe]

This bug was fixed when I upgraded to 0.9a2