Comment 6 for bug 397457

This bug being marked low has nothing to do with preference for one browser over another. There are work arounds for this issue in a webkit browser. You can disable JavaScript or append +secrecy to the bug page URL. Is this ideal? No, of course not! But we really do have many open bugs that are higher priority to me than this bug, so I set the importance to reflect this.

Now, having said that, I tagged this bug with "bug-page." The Launchpad bugs team is planning to do a focused effort during week 4 of our current cycle (the week beginning November 2) to fix all bugs tagged bug-page as part of a bug page clean up effort.

So will this bug likely be fixed soon? Yes.

However, if we miss it during the coming bug page focus week for whatever reason, then this bug (and other icon issues, annoying UI clitches, etc.) will have to be fixed around the work going on in other higher priority bugs. For that reason, I feel the importance setting is accurate for this bug.

Also, "low" has sometimes been used in the past with malone bugs to mean "good idea, but not going to happen" but this is not how we're using this importance setting now. If we're not going to fix a bug, we'll mark it "won't fix" or "invalid".

Cheers,
deryck