[Webkit-unassigned] [Bug 173878] New: Match newly-clarified spec on textarea defaultValue/value/child text content

[bugzilla-daemon at webkit.org]

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

            Bug ID: 173878
           Summary: Match newly-clarified spec on textarea
                    defaultValue/value/child text content
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Forms
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: d at domenic.me
                CC: cdumez at apple.com, wenson_hsieh at apple.com

In https://github.com/whatwg/html/issues/2752 and https://github.com/whatwg/html/issues/2750 it was discovered that various aspects of the textarea spec were confusing and did not match browser behavior (which was generally not interoperable).

In https://github.com/whatwg/html/pull/2766 we settled on a reasonable set of semantics that matched most browsers in most aspects and was simple to implement. The main changes are:

> The child text content change steps for textarea elements must, if the element's dirty value flag is false, set the element's raw value to its child text content.

> The defaultValue IDL attribute must, on getting, return the element's child text content. On setting, it must act as the setter for the element's textContent IDL attribute.

These are tested by the tests at http://w3c-test.org/submissions/6256/html/semantics/forms/the-textarea-element/value-defaultValue-textContent.html (which will eventually end up at http://w3c-test.org/html/semantics/forms/the-textarea-element/value-defaultValue-textContent.html when https://github.com/w3c/web-platform-tests/pull/6256 is merged).

Safari Tech Preview matches most aspects of the new semantics, with the following exceptions:

- The defaultValue getter should reflect the child text content, not the textContent (= "descendant text content"). This harmonizes it with what is actually rendered, and with the value property.
- The defaultValue setter should act as the textContent setter, i.e. it should wipe out all child nodes in addition to adding a new text node.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170627/35a60f84/attachment.html>