Closed
Bug 63705
Opened 24 years ago
Closed 24 years ago
Select contents of textfield in Find in this Page upon loading
Categories
(SeaMonkey :: UI Design, defect, P3)
SeaMonkey
UI Design
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bugzilla, Assigned: bugzilla)
References
Details
Attachments
(5 files)
11.63 KB,
patch
|
Details | Diff | Splinter Review | |
11.63 KB,
patch
|
Details | Diff | Splinter Review | |
6.50 KB,
patch
|
Details | Diff | Splinter Review | |
8.53 KB,
patch
|
Details | Diff | Splinter Review | |
1.66 KB,
patch
|
Details | Diff | Splinter Review |
In cases where we remember the last find text and prefill it in the Find in
this Page dialog, we should select all the text upon loading. Attaching a
patch which does this, fixes the context persistence (setting checked="" wasn't
properly pre-checking the appropriate checkboxes), and does other clean-up.
Upon fixing the persistence, I noticed that the case sensitive checkbox was
checked by default upon loading the dialog (even though I hadn't previously
checked it). After some digging, I found that mLastCaseSensitive was set to
PR_TRUE in the nsFindComponent constructor, while the other two
(mLastSearchBackwards and mLastWrapSearch) were set to PR_FALSE. Simon, cvs
blame says you did this back in 6/99 in rev. 1.19. Any idea why
mLastCaseSensitive should be PR_TRUE by default?
Assignee | ||
Comment 2•24 years ago
|
||
Assignee | ||
Comment 4•24 years ago
|
||
Comment 6•24 years ago
|
||
Doing this with code specific to the Find dialog seems unhealthy, as it implies
that every dialog will have to do the same thing -- and since this is expected
behavior for every dialog, they shouldn't really have to do it individually.
I think that (apart from the unrelated cleanup of the Find dialog, to make the
checkboxes persistent between searches) this should be a duplicate of bug 28583.
Whenever a text field takes focus, by any means other than clicking in it, its
contents should be selected.
Assignee | ||
Comment 7•24 years ago
|
||
Matthew: I'll file a bug to remove it (and the similar Open Web Location code)
once that bug is fixed. Please resummarize bug 28583 to include every case
except clicking, though (not just tabbing).
Assignee | ||
Comment 8•24 years ago
|
||
cc'ing timeless for review
MPL not NPL. Please don't use a contributor section rely on cvs blame.
i'd prefer not to give my r= until the license is settled, but if someone says
we use NPL then you can take this as my r=.
OS: Windows ME → All
Hardware: PC → All
Comment 10•24 years ago
|
||
mind doing a diff -bw so we can see what ACTUALLY changed? :)
Comment 11•24 years ago
|
||
heh, I had to use norton utilties ncompare in order to understand the changes.
Assignee | ||
Comment 12•24 years ago
|
||
Assignee | ||
Comment 13•24 years ago
|
||
Assignee | ||
Comment 14•24 years ago
|
||
alec, have time to sr this (crap) before you go vacationing?
Assignee | ||
Comment 15•24 years ago
|
||
Just noticed the modeline says C++. Fixed in my tree.
Comment 16•24 years ago
|
||
a couple of things:
+ dump("*** ERROR ACCESSING FIND COMPONENT!\n");
is this ever likely to fail, and warrant this human readable message that an
optimized build will never show unless it is run with a console? A user of a
debug build (the only one likely to see any debug output as the result of failing
to create the find component) may be more impressed with the actual js exception,
which can be obtained by removing the try... catch
also, it looks like you're setting the checked attribute on checkboxes directly..
.checked is supposed to work...
Comment 17•24 years ago
|
||
with described changes, a=ben@netscape.com
Assignee | ||
Comment 18•24 years ago
|
||
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 19•24 years ago
|
||
Reopening for a little more cleanup.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 20•24 years ago
|
||
Comment 22•24 years ago
|
||
r=jag
Assignee | ||
Comment 23•24 years ago
|
||
cc'ing ben for a= on this last bit of cleanup that clearly doesn't belong in
thsi bug ;)
Assignee | ||
Comment 24•24 years ago
|
||
Rest of cleanup checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Comment 25•24 years ago
|
||
vrfy fixed using 2001.05.29.0x comm bits on linux, winnt and mac.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•