(no longer active) Reporter
	Description • 14 years ago

NS_EVENT_STATE_MOZ_READONLY and NS_EVENT_STATE_MOZ_READWRITE are mutually exclusive, so we'd really need only one of them.  Let's remove the first one and keep the second one instead of it.

	Boris Zbarsky [:bzbarsky]
	Comment 1 • 14 years ago

David, just to make sure... there are no plans to have a situation where nodes are neither readonly nor readwrite (a la what we have with enabled/disabled), right?

	David Baron :dbaron:
	Comment 2 • 14 years ago

There hasn't been discussion of any of this stuff for ages.

	Boris Zbarsky [:bzbarsky]
	Comment 3 • 14 years ago

OK, taking.  Will fix post-2.0.

	(no longer active) Reporter
	Comment 4 • 14 years ago

Also, based on the spec changes in http://www.w3.org/Bugs/Public/show_bug.cgi?id=11554, input's and textareas should always be :read-write.

	Mounir Lamouri (:mounir)
	Comment 5 • 14 years ago

(In reply to comment #4)
> Also, based on the spec changes in
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=11554, input's and textareas
> should always be :read-write.

What do you mean? input elements are still :read-only when immutable and textarea when they have the disabled or readonly attribute set.

	(no longer active) Reporter
	Comment 6 • 14 years ago

(In reply to comment #5)
> (In reply to comment #4)
> > Also, based on the spec changes in
> > http://www.w3.org/Bugs/Public/show_bug.cgi?id=11554, input's and textareas
> > should always be :read-write.
> 
> What do you mean? input elements are still :read-only when immutable and
> textarea when they have the disabled or readonly attribute set.

Yeah, sorry, I meant that whether they're in an edit host or not doesn't matter any more.  I should have not assumed that "always" conveys that meaning!  :-)

	Boris Zbarsky [:bzbarsky]
	Comment 7 • 13 years ago

In case someone wants to steal this, see bug 562169 comment 9.

	Firefox Bug Husbandry Bot
	Comment 8 • 6 years ago

Bulk priority change, per :mdaly