Closed Bug 244835 Opened 21 years ago Closed 21 years ago

Regular expression in searching in the page

Categories

(SeaMonkey :: UI Design, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 32641

People

(Reporter: bugzilla, Assigned: jag+mozilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; cs-CZ; rv:1.7) Gecko/20040514 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; cs-CZ; rv:1.7) Gecko/20040514 There would be nice to have a regular expression possibility in the searching in the page (this can concern not only Browser, but Editor and Mail too). The dialog "Find on the page" should have 4th checkbox "Regular expression" and when it is checked the searching will use regular expression search. MS Word and OpenOffice.org Writer have it so! Well, most users are using classical search (simple text), but on the search dialog of MS Word and OpenOffice.org Writer, there is checkbox for regular expression search, so experienced users can use it 8-) Mozilla understands regular expressions. So I hope, there is no problem for implementing this. Yes, of course, there are some questions how to implement some more problematic cases like: a) Moz<b>illa</b> <- should this be handled as Mozilla (on word) or two words Moz and illa. b) How to handle ^ and $ - probaly as the begining and the end of the paragraph (OpenOffice.org has it so) - but what exactly is a paragraph? Only the text between <p> and </p> tags? Or everything, what have display:block ? But I think that the most of the syntax is clear and without problems see: [df]og Java(Script)? (.)(.).\2\1 <- (pallindrom ;-) bug [1-2][0-9][0-9] etc. etc. etc. Reproducible: Always Steps to Reproduce:
*** This bug has been marked as a duplicate of 32641 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
v=aha
Status: RESOLVED → VERIFIED
Summary: Regular expession in searching in the page → Regular expression in searching in the page
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.