I think it's ok to keep WML code if we can avoid the form control issue.
We can terminate the form control abstraction for HTML and WML. e.g.
- Merge dom/InputElement to html/HTMLInputElement
- Merge dom/InputElement to wml/WMLInputElement
- Remove dom/InputElement
- Copy RenderTextControlSingleLine as RenderTextControlWML
- RenderTextControlSingleLine only supports HTMLInputElement
- RenderTextControlWML only supports WMLInputElement
We would have some duplicated code. But it would be better than the current
situation.
On Fri, Apr 8, 2011 at 10:08, Darin Adler <[email protected]> wrote:
On Apr 8, 2011, at 2:09 AM, Ryosuke Niwa wrote:
> We have been discussing the possibility of dropping WML support in
WebKit
on IRC for a while now because
> • None of core ports (Mac, Windows, GTK, Qt, & Chromium) use it by
default
> • Maintenance cost is high
I’ll just add one other thing: HTML form element implementations have
factoring that are twisted and complicated because of WML in a way that
makes working on those classes unpleasant for me. It would make form work
considerably easier if we drop WML support.
-- Darin
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
--
TAMURA Kent
Software Engineer, Google
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
