Match newly-clarified spec on textarea defaultValue/value/child text content

Confirmed Issue #12518762 • Assigned to Luis S.


Domenic D.
Jun 27, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

In and it was discovered that various aspects of the textarea spec were confusing and did not match browser behavior (which was generally not interoperable).

In 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 (which will eventually end up at when is merged).

Edge seems to have a very broken defaultValue getter, causing almost all of the tests to fail.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Assigned To to “Bogdan B.”

      Changed Assigned To from “Bogdan B.” to “Travis L.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Travis L.” to “Luis S.”

    You need to sign in to your Microsoft account to add a comment.

    Sign in