The short-term fix for this problem would be to update the localconfig.js file on b.m.o (removing the "flash" keyword entry there). Attachment 46089 [details] [diff] in bug 61561 is a patch that brings the keyword list a bit more up-to-date, but doesn't fix that "flash" problem yet. It would be easy to create an updated patch that takes care of the "flash" problem, too, but I can't see why I should do that since nobody cares to apply it to b.m.o anyway. The long-term fix for this problem is the patch provided in bug 72837 to generate a JS file with the keyword list automatically. I'm marking this bug dependent on that one for now.
Depends on: 72837
This looks similar to bug 69621. Is it the same, or dependent? Will fixing that automagically fix this too?
No this is unrelated. This will also be a problem for resolutions once customised resolutions (bug #94534) lands.
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.16
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Summary: quicksearch does not have updated keyword list for JS → quicksearch does not have updated keyword, resolution, etc list for JS
This is basically being done as a part of bug #70907, so replacing the dependency on bug #72837 with it.
All 2.18 bugs that haven't been touched in over 60 days and aren't flagged as blockers are getting pushed out to 2.20
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to firstname.lastname@example.org or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.
Target Milestone: Bugzilla 2.20 → ---
Reassigning bugs that I'm not actively working on to the default component owner in order to try to make some sanity out of my personal buglist. This doesn't mean the bug isn't being dealt with, just that I'm not the one doing it. If you are dealing with this bug, please assign it to yourself.
Assignee: justdave → general
QA Contact: mattyt-bugzilla → default-qa
Assignee: general → wurblzap
Whiteboard: [blocker will fix]
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Bugzilla 2.22
Created attachment 644808 [details] [diff] [review] changeset: :8571114112b2 This patch doesn't break robocop/mochitest
Comment on attachment 644808 [details] [diff] [review] changeset: :8571114112b2 Wow, bzexport fail.
You need to log in before you can comment on or make changes to this bug.