This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.


This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

The user-modify property has no effect in Firefox. It was originally planned to determine whether or not the content of an element can be edited by a user.

/* Keyword values */
user-modify: read-only;
user-modify: read-write;
user-modify: write-only;

/* Global values */
user-modify: inherit;
user-modify: initial;
user-modify: unset;

This property has been replaced by the contenteditable attribute.


The -moz-user-modify property is specified as one of the keyword values from the list below.


Default value. Contents are read-only.
The user is able to read and write contents.
read-write-plaintext-only This API has not been standardized.
Same as read-write, but rich text formatting will be lost.
The user is able to edit the content, but not to read it.

Formal definition

Value not found in DB!

Formal syntax




<div class="readwrite">The user is able to change this text.</div>


.readwrite {
  -moz-user-modify: read-write;
  -webkit-user-modify: read-write;


Not part of any standard. A similar property, user-focus, was proposed in early drafts of a predecessor of the CSS3 UI specification, but was rejected by the working group.

Browser compatibility

BCD tables only load in the browser

See also