Is Gecko's weird rendering of this actually right?
Gus Richter
https://bugzilla.mozilla.org/show_bug.cgi?id=320344
No comments, unconfirmed or lack of interest meaning that Moz folks
believe that all is OK in Moz-CSS2.1 land or is there nobody that cares?
--
Gus
Boris Zbarsky
> No comments, unconfirmed or lack of interest meaning that Moz folks
> believe that all is OK in Moz-CSS2.1 land or is there nobody that cares?
I marked the bug as depending on the reflow branch landing, no? See the status
whiteboard.
-Boris
Gus Richter
Thank you very much. I thought that it was being ignored.
I thought that on any change on bugs, all on the mailing list get
notified of such - I reveived none!
So [reflow-refactor] entered in Status Whiteboard means a dependancy?
What is the best way to know when "reflow branch" has landed and/or the
status thereof?
--
Gus
Boris Zbarsky
> I thought that on any change on bugs, all on the mailing list get
> notified of such - I reveived none!
It depends on your email settings in Bugzilla.
> So [reflow-refactor] entered in Status Whiteboard means a dependancy?
It means that the bug looks like something that has a good chance of getting
fixed by the reflow branch.
> What is the best way to know when "reflow branch" has landed and/or the
> status thereof?
People will start going through the "[reflow-refactor]" bugs and either
resolving them as fixed or working on them. ;)
Also possible is that actual dependencies will be added once a bug to land the
branch is filed....
-Boris
Gus Richter
> Gus Richter wrote:
>> I thought that on any change on bugs, all on the mailing list get
>> notified of such - I reveived none!
>
> It depends on your email settings in Bugzilla.
I get all others. I went to check and I did get that particular one. I
just mistook it as someone adding onto the mailing list. Doesn't matter
since I didn't, and still don't, really understand "Whiteboard".
>> So [reflow-refactor] entered in Status Whiteboard means a dependancy?
>
> It means that the bug looks like something that has a good chance of
> getting fixed by the reflow branch.
I thought you were talking about a particular branch, a "reflow branch"
as in trunk/branch.
>> What is the best way to know when "reflow branch" has landed and/or
>> the status thereof?
>
> People will start going through the "[reflow-refactor]" bugs and either
> resolving them as fixed or working on them. ;)
So you are actually talking about several bugs tagged as
"[reflow-refactor]" bugs.
I hope that "reflow-refactor" does not mean "redraw" because then I
believe that this bug does not apply. Bug 300909 does in that sense.
Boris Zbarsky
>> It means that the bug looks like something that has a good chance of
>> getting fixed by the reflow branch.
>
> I thought you were talking about a particular branch, a "reflow branch"
> as in trunk/branch.
Yes. It's a particular branch. Or rather particular set of branches... The
current one, I believe, is REFLOW_20060302_BRANCH. See
http://wiki.mozilla.org/Gecko:Reflow_Refactoring for more information.
> So you are actually talking about several bugs tagged as
> "[reflow-refactor]" bugs.
A whole slew, actually.
> I hope that "reflow-refactor" does not mean "redraw" because then I
> believe that this bug does not apply.
It means "change how layout works".
-Boris
Gus Richter
>
> Yes. It's a particular branch. Or rather particular set of branches...
> The current one, I believe, is REFLOW_20060302_BRANCH. See
> http://wiki.mozilla.org/Gecko:Reflow_Refactoring for more information.
Thank you for the link, your time and explanations.
Very much appreciated.
--
Gus
Dan Veditz
> I didn't, and still don't, really understand "Whiteboard".
It's a blank slate of last resort for adding status notations that don't
fit elsewhere in the bugzilla schema. Generally best left to the
developers working on the bug.
I'm surprised this case didn't use a dependency on a meta bug instead.