[Webkit-unassigned] [Bug 103513] Provide the backend for exposing the layer tree to the Web Inspector

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Nov 28 14:18:42 PST 2012


https://bugs.webkit.org/show_bug.cgi?id=103513





--- Comment #17 from Pavel Feldman <pfeldman at chromium.org>  2012-11-28 14:20:55 PST ---
> In my opinion, this is not too different from the V8 centric features that have been added to the protocol. Those are changes that benefit only one port — Chromium — and add maintenance cost to the project as a whole. Your port does maintain those parts, but the burden is mostly on other ports to make them work for JSC.

I don't think this analogy applies. In case of V8 vs JSC:
- Both front-end and backend were open source, belonging to WebKit
- We were on the best-effort path wrt having JSC supported
- Most of the features are now supported in JSC

In this case, we are talking about:
- Proprietary front-end putting maintenance cost on the WebKit
- No intention to contribute front-end to WebKit
- No clear plan for these features to be ever supported in WebKit inspector

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list