From e75e6d0f714e77b1d7b700dca62aba0fd9a5385d Mon Sep 17 00:00:00 2001
From: "bbaetz%student.usyd.edu.au" <>
Date: Mon, 15 Apr 2002 09:47:52 +0000
Subject: Bug 129442 - make html of a default installation (mostly) HTML 4.01
transitional compliant Original patch by chema@ximian.com, modified/extended
by bbaetz@student.usyd.edu.au r=gerv, justdave
---
quicksearch.html | 75 +++++++++++++++++++++++++++++++-------------------------
1 file changed, 41 insertions(+), 34 deletions(-)
(limited to 'quicksearch.html')
diff --git a/quicksearch.html b/quicksearch.html
index df7e85ccf..1b1ecb1a6 100644
--- a/quicksearch.html
+++ b/quicksearch.html
@@ -1,88 +1,95 @@
+
+
Bugzilla QuickSearch
+
If you are already familiar with the original
Bugzilla Query Form,
you may prefer this form.
+
-
-
-
+
+
Bugzilla QuickSearch
+
Type in one or more words (or word fragments) to search for:
+
-
-
Getting Started
- This is case-insensitive search.
- table , Table
- and TABLE are all the same.
+ and TABLE are all the same.
+
- This is all words as substrings search.
Therefore you should use stems to get better results:
- Use localiz instead of localize or
- localization.
+ localization.
- Use bookmark instead of bookmarks or
- bookmarking.
+ bookmarking.
+
-
-Features
+
- Boolean operations: ``-foo''(NOT), ``foo bar''(AND),
``foo|bar''(OR).
- NOT: Use -foo to exclude bugs
- with foo in the summary.
-
- AND: Space-separated words are treated as a conjunction.
-
- OR: Within a word, "|"-separated parts denote alternatives.
-
- Besides "|", a comma can be used to separate alternatives.
-
- OR has higher precedence than AND; AND is the top level operation
+ with foo in the summary.
+ - AND: Space-separated words are treated as a conjunction.
+ - OR: Within a word, "|"-separated parts denote alternatives.
+ - Besides "|", a comma can be used to separate alternatives.
+ - OR has higher precedence than AND; AND is the top level operation
Example: url,location bar,field -focus
means
- (url OR location) AND (bar OR field) AND (NOT focus)
-
-
- Use +foo to search for bugs where the summary contains foo as a substring.
+ (url OR location) AND (bar OR field) AND (NOT focus)
+
+
+- Use +foo to search for bugs where the summary contains foo as a substring.
Use #foo to search for bugs where the summary contains the word foo
- - +brow does not find all bugs in the Browser product
-
- #title does not find bugs bugs with titlebar or titled
+
- +brow does not find all bugs in the Browser product
+ - #title does not find bugs bugs with titlebar or titled
Phrases with special chars (space, comma, +, -, #, ...) can be quoted:
- - "lock icon"
+
- "lock icon"
+
- Open vs. Resolved Bugs:
By default, only open (i.e. unresolved) bugs are shown.
Use +DUP as first word in your query
@@ -92,10 +99,10 @@ document.forms['f'].id.focus();
regardless of status or resolution. Searching for duplicates is
recommended if you can't find an open bug directly.
- - +DUP,FIXED table border
-
- ALL mouse wheel
+
- +DUP,FIXED table border
+ - ALL mouse wheel
-
+
- Focus the Search with Products & Components:
To search for bugs in product "Foo Bar" only, add
:foo or :bar or both
@@ -103,6 +110,7 @@ document.forms['f'].id.focus();
You can do this with any substring of a
product or component
to focus the search.
+
More Tips
@@ -110,19 +118,21 @@ document.forms['f'].id.focus();
- You can also use this tool to lookup a bug by its number.
+
- A comma-separated list of bug numbers gives you a list of these bugs.
- - 12345,23456,34567
+
- 12345,23456,34567
+
By default, the following fields are searched: Summary, Keywords, Product,
Component, Status Whiteboard. If a word looks like a part of a URL, that field
is included in the search, too.
-
+
+
Use the powerful
Bugzilla Query Form
for advanced queries.
+
-
-
-
-
-
--
cgit v1.2.3-24-g4f1b