Bug 142477 – formerly-readonly <input> doesn't display cursor when focused

• Status: RESOLVED
• Resolution: CONFIGURATION CHANGED
• Component: Forms

[Chris Rebert]

Steps to reproduce:
1. Open http://jsfiddle.net/2matzLja/1/show/ in Safari 8.0.3
2. Double-click on the <input>. Note that a focus ring is displayed on it.

Expected result:
A text cursor should be displayed in the <input>, just as with a normal has-always-been-writeable <input>.

Actual result:
No text cursor is displayed in the <input>.
However, you can still type in the <input>, and as soon as you type a character into the <input>, the text cursor starts being displayed.

Other details:
The example's source code can be viewed at http://jsfiddle.net/2matzLja/1/
Original Bootstrap bug report: https://github.com/twbs/bootstrap/issues/16022
Related Chrome bug: https://code.google.com/p/chromium/issues/detail?id=465274

[Chris Rebert]

Created attachment 252551 [details]
Copy of JS Fiddle example

[Chris Rebert]

Also filed a Radar for this:

<rdar://problem/20090003>

[Chris Rebert]

Still reproduces in Safari 9.0.3

[Ahmad Saleem]

I am not able to reproduce this bug in Safari 15.6.1 on macOS 12.5.1 using attached test case and it does show "Typing Caret" and  "Editing - I" cursor when on the field and it does disappear like all other browser as soon as you start typing.

It matches with all other browsers (Chrome Canary 107 and Firefox Nightly 106).

But I will not close this bug because I noticed strange behavior in case of Firefox where if I activate it and type something and then refresh browser, it will still keep what I have written in the field even within Private Window. I don't know whether it is web-spec and both Chrome and Safari are wrong or it is "Firefox" is wrong.

So I will leave it to someone else to confirm this bug (which is not this bug about) but still want to share updated testing results. Thanks!

[Alexey Proskuryakov]

Restoring form content on reload would be a browser behavior outside web specification purview. I don't think that we need to track that difference as a bug.

There is a long discussion in https://bugzilla.mozilla.org/show_bug.cgi?id=46845 which I didn't read.

Marking as Config Changed, as the original issue reported here no longer reproduces.