No entry in Status Whiteboard for this one.
Why does the Status remain UNCONFIRMED for this and id=320344 ?
Other than Bernd's comment of similarity to a bug that he is assigned
on, there is no other. Am I correct in assuming that this means that
"wait for bug 206516 to be resolved and then see if bug 300909 will
perchance also be resolved?"
--
Gus
Except the dependency I added on bug 162063 sometime back in November...
> Am I correct in assuming that this means that
> "wait for bug 206516 to be resolved and then see if bug 300909 will
> perchance also be resolved?"
The dependency means "This will probably be fixed once bug 162063 is fixed" in
this case. (It could also mean "this can be worked on once bug 162063 is
fixed", but it doesn't in this case.)
But none of these are really "Is Gecko's weird rendering actually right?"
questions. They're "is my bug going anywhere?" questions. The answer to that
is usually "maybe". ;)
-Boris
My face is red, since I failed to notice this one as well.
> But none of these are really "Is Gecko's weird rendering actually
> right?" questions. They're "is my bug going anywhere?" questions. The
> answer to that is usually "maybe". ;)
Just getting your attention and learning, thanks.
BTW, why have these two not been confirmed?
--
Gus
Lots of people help by looking at the recent incoming bugs; lots of
developers don't look at unconfirmed bugs since there are always more
confirmed ones needing work. If a bug remains unconfirmed a month or two
there's a decent chance it will slide out of notice and never get
confirmed. The best thing to do in those cases is exactly what you've
done -- champion the bugs outside bugzilla to get someone to take a
second look.