yurys at chromium.org
Sat Nov 13 23:47:01 PST 2010
I don't think there is a particular person who maintains that option.
Instead if you cannot find the change which broke it and file a bug against
the author you could file a bug against the web inspector component(
webkit.org/new-inspector-bug) and we'll take care of it.
In this particular case it was my change
http://trac.webkit.org/changeset/71515 that broke it. I didn't see the
failure because I tried to build webkit with --minimal option(and it was
fine) which is usually enough but apparently not in this case.
On Sun, Nov 14, 2010 at 2:38 AM, Patrick Gansterer <paroga at paroga.com>wrote:
> I filed bug 49500 (including patch).
> But I'm still interested if there is someone who "maintains" the
> ENABLE(INSPECTOR) option.
> Simon Fraser:
> > Please file a bugzilla bug on this issue.
> > Simon
> > On Nov 13, 2010, at 8:15 AM, Patrick Gansterer wrote:
> >> Hi,
> >> Does anybody compile WebKit with inspector disabled?
> >> It's not possible with the current trunk (since weeks). I'm not sure
> what's the correct solution to fix this.
> >> The main problem is that Console.cpp (e.g. at ) uses ScriptCallStack
> and ScriptCallStackFrame, but this classes should go into a "#if
> ENABLE(INSPECTOR)" section IMHO.
> >> Otherwise they must not use any classes from InspectorValues (e.g. at
> >> Can someone fix this (or at least point me to the right solution)?
> >> 
> >> 
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev