I'm not trying to turn this into a huge deal. I've already filed a
bug<http://crbug.com/8662>and am likely to move on for now. But for me
it's just another issue that
users are going to complain about that I'm going to need to fix someday.
Avi
/who bets the first complaint will be from a Mac user rather than a Windows
one
On Wed, Mar 11, 2009 at 2:12 PM, Brett Wilson <bre...@chromium.org> wrote:
> On Wed, Mar 11, 2009 at 10:11 AM, Amanda Walker <ama...@chromium.org>
> wrote:
> > On Wed, Mar 11, 2009 at 2:07 PM, Brett Wilson <bre...@chromium.org>
> wrote:
> >> Do you mean when you click on the menu, blocking the browser until the
> >> renderer responds with whether the menus can be enabled? I would be
> >> opposed to that.
> >
> > So are we, but that's what WebKit currently assumes. That's why we've
> > been trying to brainstorm a way around it.
>
> This seems like it is not worth worrying about until the mac browser
> is as good as the Windows one. We have this "bug" on Windows, and it's
> not held anything up so far.
>
> Brett
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
