On Jul 10, 2010, at 1:17 AM, Alex Milowski wrote:
I would think we'd close it when we've actually completely implemented
MathML.
If this is what you want the bug to represent, then it does make sense to keep
all feature-implementation bugs related to this master bug, but none of the bug
Le 12 juil. 2010 à 21:01, Beth Dakin a écrit :
On Jul 10, 2010, at 1:17 AM, Alex Milowski wrote:
I would think we'd close it when we've actually completely implemented
MathML.
If this is what you want the bug to represent, then it does make sense to
keep all feature-implementation
On Jul 12, 2010, at 11:01 AM, Beth Dakin wrote:
On Jul 10, 2010, at 1:17 AM, Alex Milowski wrote:
I would think we'd close it when we've actually completely implemented
MathML.
If this is what you want the bug to represent, then it does make sense to
keep all feature-implementation
On Mon, Jul 12, 2010 at 7:49 PM, Maciej Stachowiak m...@apple.com wrote:
I think it's fine to enable MathML soon, as long as we make sure of the
following:
1) Using a MathML-enabled build shouldn't cause stability problems or
functional or performance regressions when browsing ordinary
On Jul 12, 2010, at 4:06 PM, Alex Milowski wrote:
On Mon, Jul 12, 2010 at 7:49 PM, Maciej Stachowiak m...@apple.com wrote:
I think it's fine to enable MathML soon, as long as we make sure of the
following:
1) Using a MathML-enabled build shouldn't cause stability problems or
On Sat, Jul 10, 2010 at 2:19 AM, David Kilzer ddkil...@webkit.org wrote:
IMO, it should be closed once MathML is enabled in the WebKit nightly builds
and/or most ports.
I would think we'd close it when we've actually completely implemented
MathML. Just
enabling it seems like something we
On Sat, Jul 10, 2010 at 2:24 AM, Adam Barth aba...@webkit.org wrote:
Out of curiosity, is there an estimate of when that might be? There's
some interaction with the new HTML5 parser because it supports
MathML-in-HTML.
That's something we're trying to get a handle on right now. Sausset
For MathML we have a master bug 3251 that we've been making depend
on every new patch for MathML. That is a very nice in that as new patches
are added and committed, you can get notifications of the changes
in status.
We also have the MathML component that all bugs should be associated
with. As
On Jul 9, 2010, at 6:23 AM, Alex Milowski wrote:
For MathML we have a master bug 3251 that we've been making depend
on every new patch for MathML. That is a very nice in that as new patches
are added and committed, you can get notifications of the changes
in status.
If all you're concerned
On Jul 9, 2010, at 7:34 AM, Adam Roben wrote:
I think an important question to ask is, When will you move the master bug
to Resolved/Fixed? This is basically another way of saying, What task(s)
does the master bug represent? Once you know that answer, the answers to
your other questions
On Jul 9, 2010, at 7:34 AM, Adam Roben aro...@apple.com wrote:
On Jul 9, 2010, at 6:23 AM, Alex Milowski wrote:
Should we keep the master bug?
Should we use it only for our implementation efforts and not
make it depend on every random bug filed for the MathML
component?
I think an
On Fri, Jul 9, 2010 at 6:19 PM, David Kilzer ddkil...@webkit.org wrote:
On Jul 9, 2010, at 7:34 AM, Adam Roben aro...@apple.com wrote:
On Jul 9, 2010, at 6:23 AM, Alex Milowski wrote:
Should we keep the master bug?
Should we use it only for our implementation efforts and not
make it
12 matches
Mail list logo
