QuickSearch does not comply with W3C DOM spec

RESOLVED FIXED in Bugzilla 2.22

Status

()

P1
enhancement
RESOLVED FIXED
18 years ago
6 years ago

People

(Reporter: caillon, Assigned: Wurblzap)

Tracking

2.15
Bugzilla 2.22
Dependency tree / graph

Details

(Whiteboard: [blocker will fix], URL)

Attachments

(1 attachment, 1 obsolete attachment)

This *could* be evangelism but I'll file it under Bugzilla ;-)

Currently the JS above will not work for DOM enabled browsers.  I will attach a
patch to fix that.

CCing default Tech Evangelism/US English owners for QA.
Created attachment 48255 [details] [diff] [review]
Patch for DOM-alizing the quicksearch
Status: NEW → ASSIGNED
Keywords: patch, review
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.16
Created attachment 48256 [details] [diff] [review]
There were some unwanted tabs in last patch. This removes them.
Attachment #48255 - Attachment is obsolete: true
I've done a search thru more files and found some others that exhibit bad DOM

In customised version of Bugzilla, this can cause certain javascripts to fail to
work at all with Mozilla.  (which is how I noticed this).  Here is a list of
files that I've found to contain proprietary DOM include:

bug_form.pl
buglist.cgi
index.html
query.cgi
queryhelp.cgi
quicksearch.html
quicksearchhack.html

Note: since we aim for browser backward compatibility in Bugzilla, I included a
check for if the browser is DOM capable, we use DOM and if not, use the old
proprietary behaviour.

My JS Console will be much happier once this is finally fixed :)

More patches to come!
Severity: normal → major
Keywords: patch, review
Priority: P3 → P1
the *.atml files for the attachment templates also suffer from bad DOM.
I agree that the code is bad (document.f.id.value, in several places). However,
before fixing it the way you suggest it, I'd very much like to see the fix to
bug 76484 (alias attachment 40917 [details] [diff] [review] in bug 37339) checked in, because it
eliminates the bad code from quicksearch.js altogether. (Ok, it just moves the
problem to different places, but I think it's worth the wait.)
Summary: bugzilla.mozilla.org - does not comply with W3C DOM spec → QuickSearch does not comply with W3C DOM spec
No longer depends on: 96983
caillon: feel like splashing this patch's face with water and waking it up?

Gerv
Keywords: patch, review
ping caillon...
Keywords: patch, review
Per caillon in IRC, this is actually a Mozilla problem, but we should still fix
this to work around it.  I'll let him do the explaining if anyone has any
complaints...
Severity: major → enhancement
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18

Comment 9

17 years ago
Bug 70907 is also targeted for 2.18 which would eliminate the QuickSearch 
JavaScript and make it server side perl (giving it a larger usable audience 
and reducing page load time).
Comment on attachment 48256 [details] [diff] [review]
There were some unwanted tabs in last patch. This removes them.

This code isn't there anymore.

Is there still work to be done, or should this bug be closed?
Attachment #48256 - Flags: review-
Sigh.  No time to work on this anymore...  ->Default owner.
Assignee: caillon → endico
Status: ASSIGNED → NEW
Assignee: endico → nobody
enhancements without current patches are being pushed to 2.20
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
(Assignee)

Updated

14 years ago
Depends on: 70907
(Assignee)

Updated

14 years ago
Assignee: nobody → wurblzap
Whiteboard: [blocker will fix]
(Assignee)

Updated

14 years ago
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.