- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Fri, 08 Oct 2010 19:24:01 +0900
- To: Ehsan Akhgari <ehsan@mozilla.com>
- CC: Richard Ishida <ishida@w3.org>, "Aharon (Vladimir) Lanin" <aharon@google.com>, aronovitch@gmail.com, public-i18n-bidi@w3.org
On 2010/10/07 8:55, Ehsan Akhgari wrote: > On Wed, Oct 6, 2010 at 12:29 PM, Richard Ishida<ishida@w3.org> wrote: > >> I agree that we should not lose these things. We should probably also >> consider contacting browser implementers directly with some of this stuff, >> rather than just allow Hixie to be the gate-keeper. >> > > I think it's best for us to wait until all of the issues are resolved As for entering into bug databases, it may make sense to put in a bug already, with a lower priority or later target, and then escalate the bug (or delete it) once things get shaken out. That way, we raise awareness of other browser developers and may get some valuable feedback. As for contacting Microsoft and Opera, the earlier the better. Things may work much better if they feel involved than if they get the impression that decisions were made without them. You might also get valuable input from them, too. Regards, Martin. > (either accepted into the spec, rejected, or moved to other specs such as > CSS), and then given that list, start filing bugs for the browser engines > with publicly accessible bug databases (Gecko and Webkit to the best of my > knowledge) and also start contacting Microsoft and Opera about this and try > to get them to implement the proposals as well. > > I volunteer to file the appropriate Gecko and Webkit bugs myself. I may > also get around to implement some of this for Gecko as well (after Firefox 4 > is released, of course). > > Cheers, > -- > Ehsan > <http://ehsanakhgari.org/> > -- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jp
Received on Friday, 8 October 2010 10:24:46 UTC