[Webkit-unassigned] [Bug 64761] New: Let's kill window.find()

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jul 18 16:01:01 PDT 2011


           Summary: Let's kill window.find()
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ian at hixie.ch
                CC: hyatt at apple.com, mjs at apple.com, fishd at chromium.org

window.find() has a number of bugs:

 - first argument being blank doesn't show a dialog like Gecko.
 - when aCaseSensitive is false, even "å" matches "a".
 - once find() has selected text in a text field, the next search restarts at the top of the page
 - aWholeWord has no effect
 - aSearchInFrames has no effect (unlike Gecko)
 - aShowDialog doesn't work (unlike Gecko)
 - calling window.find() on a loading doc doesn't work

That's just the bugs I found in the first few minutes of testing.

This legacy feature seems to have no real use case, is very poorly implemented, and is badly designed in the first place (six boolean arguments?). It's only implemented in Gecko and WebKit.

Can we drop it?

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list