Closed
Bug 98307
Opened 24 years ago
Closed 20 years ago
QuickSearch does not comply with W3C DOM spec
Categories
(Bugzilla :: Query/Bug List, enhancement, P1)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.22
People
(Reporter: caillon, Assigned: Wurblzap)
References
()
Details
(Whiteboard: [blocker will fix])
Attachments
(1 file, 1 obsolete file)
2.57 KB,
patch
|
bbaetz
:
review-
|
Details | Diff | Splinter Review |
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.
Reporter | ||
Comment 1•24 years ago
|
||
Reporter | ||
Updated•24 years ago
|
Reporter | ||
Comment 2•24 years ago
|
||
Reporter | ||
Updated•24 years ago
|
Attachment #48255 -
Attachment is obsolete: true
Reporter | ||
Comment 3•24 years ago
|
||
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!
Reporter | ||
Comment 4•24 years ago
|
||
the *.atml files for the attachment templates also suffer from bad DOM.
Comment 5•24 years ago
|
||
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.)
Updated•24 years ago
|
Summary: bugzilla.mozilla.org - does not comply with W3C DOM spec → QuickSearch does not comply with W3C DOM spec
Comment 6•24 years ago
|
||
caillon: feel like splashing this patch's face with water and waking it up?
Gerv
Updated•24 years ago
|
Comment 8•23 years ago
|
||
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•23 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 10•23 years ago
|
||
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-
Reporter | ||
Comment 11•23 years ago
|
||
Sigh. No time to work on this anymore... ->Default owner.
Assignee: caillon → endico
Status: ASSIGNED → NEW
Updated•22 years ago
|
Assignee: endico → nobody
Comment 12•21 years ago
|
||
enhancements without current patches are being pushed to 2.20
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 13•21 years ago
|
||
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•20 years ago
|
Assignee: nobody → wurblzap
Whiteboard: [blocker will fix]
Assignee | ||
Updated•20 years ago
|
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•