Webkit gatekeepers may not accept your patch but they can't stop you from forking it. If you maintain a fork and you're feature becomes popular then eventually

Webkit gatekeepers may not accept your patch but they can't stop you from forking it. If you maintain a fork and you're feature becomes popular then eventually your fork will get merged into mainline webkit. If it doesn't become popular then it probably didn't need to get merged into webkit. This is how open source works and it's a good thing. It allows ideas to compete. And while we are on the subject it seems like people are talking past each other in this debate. 1a. Web standards are good because they provide a baseline of combatibility for browsers. 1b. Webkit forks on all browsers could be good because it would provide a baseline of compatibility for all browsers. 2a. Web standards could be good because they prevent any one browser from setting defacto proprietary standards that lock other browsers out of the market. 2b. Webkit on all browsers could be good because it would prevent any browser from setting defacto proprietary standards that lock other browsers out of the market. 3a. Having webkit on all browsers would hurt standards by becoming a defacto standard providing a baseline of compatibility between browsers and still allowing competition. 3b. Having webkit on all browsers would provide a real baseline of compatibility between browsers while still allowing competition. It's a little bit funny to watch actually.