[Webkit-unassigned] [Bug 34464] Chromium should receive checkbox state changes

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 2 22:30:46 PST 2010


Darin Fisher (:fishd, Google) <fishd at chromium.org> changed:

           What    |Removed                     |Added
                 CC|                            |fishd at chromium.org

--- Comment #5 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2010-02-02 22:30:44 PST ---
(In reply to comment #4)
> This change needs to be committed with a parallel change in Chromium. As I
> understand it this should NOT be added to the commit-queue as both changes are
> needed.

Hi Chris,

Is it possible to break this change up into two parts so that you can avoid the
need for a two-sided patch landing?  Generally speaking, we try to preserve the
old API while introducing the new side-by-side.  Then, once Chromium adopts the
new API, we can go back to WebKit and remove the old API.  Is that possible in
this case?

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