138066 - -moz-user-input no caret for input field.

Status: NEW

(Core :: DOM: Editor, defect, P4)

Description

[Peter Wilson]

Build 2002041509
An xhtml element with CSS3 style -moz-user-input is indeed editable. but no 
caret appears when the field receives the focus.

I know this is under development - this is just for the record.

Comment 1

[Simon Fraser [no longer active]]

Testcase please. I was not aware that -moz-user-input made anything editable
that was not already editable.

Comment 2

[Peter Wilson]

Attachment: Testcase for -moz-user-* styles.

It appears that it is the -moz-user-modify style that might be at fault. The
input field never seems to aquire the enabled state. It does acquire the focus
as specified. I am using the values from the CSS3 spec. (I hope).

Comment 3

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Don't count on user-{input,modify,etc.} being in future versions of the CSS3 UI
module.

Comment 4

[Peter Wilson]

I hope that what is already there can be made to work in the interim.
I am writing an XML editor and have a fair prototype working.
The user-input/focus/modify styles come very close to what I require:
the ability to have variable length input fields that can handle single 
line/multi line input. I would hate to have to wait another year for the 
ultimate in editbility to arrive.

Comment 5

[Boris Zbarsky [:bzbarsky]]

confirming that there is a real issue that needs addressing here.

Comment 6

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

->Editor:Core.  Note though that these properties may not be in future versions
of CSS3 drafts.

Comment 7

[Anne (:annevk)]

Attachment: test case

Comment 8

[Peter Wilson]

I know CSS3 is still not resolved, but is there any chance of getting this
working? Development of an XUL IDE foundered on this bug two years ago.  I would
like to restart the project, but this feature is a must have for editor
development. Without a caret a text editor is worthless.

Comment 9

[Anne (:annevk)]

You might want to push Ian Hickson a bit on writing the specification about it
<http://whatwg.org/specs/web-controls/current-work/> and providing feedback on
the WHATWG mailing list. I'm not aware of any other method that may speed up the
process of this bug.

Comment 10

[Peter Wilson]

Attachment: A screen shot of the XML editor with a RelaxNG grammar for XUL.

The highlighted ns attribute of the grammar element is input capable but lacks
a caret.

Comment 11

[Hixie (not reading bugmail)]

I think we should WONTFIX this particular request in favour of contentEditable.

Having a CSS property control whether something is editable or not doesn't
really make sense -- it's not a stylistic thing, it's a content thing.

Comment 12

[Peter Wilson]

I've just discovered that you need to hit function key F7 to make the caret
visible. This feature has always worked. WTF. I abandonned develpment of an XUL
IDE becuse of this. I've just wasted three years in which I could have been
working on that IDE. What a stupid f**king feature!