Hi Hema, If you are talking about WebKit and HTML, it already does it for some of its built-in HTML elements.
Some UI controls, which are modal and don't fit into the page layout, are implemented using native UI controls. These modal controls shouldn't constrained by WebKit rendering area like iframes. In such case, OS native controls are suited. File chooser is a perfect example of this. Some other controls like progress bars and spin buttons are implemented using Shadow DOM. They aren't modal and need to be parts of the page layout. The decision which of native-controls/shadow-dom should be used for implementing HTML form controls is case by case and in't that simple. You can see how <input> element is implemented. When you try to implement any new control for HTML, it would be good to file a bug and have further discussion there. See http://www.webkit.org/coding/adding-features.html If you are talking about Web-app or JS library development, webkit-dev isn't a place for that. Sites like stackoverflow.com will work well. There are also some good tutorials. For example: http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom/ Hope this helps. -- morrita
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-dev
