142477 2015-03-09 03:36:29 -0700 formerly-readonly <input> doesn't display cursor when focused 2022-08-30 14:03:46 -0700 1 1 1 Unclassified WebKit Forms WebKit Nightly Build Mac (Intel) OS X 10.11 RESOLVED CONFIGURATION CHANGED http://code.google.com/p/chromium/issues/detail?id=465274 http://jsfiddle.net/2matzLja/1/ HasReduction P2 Normal --- 1 webkit webkit-unassigned ahmad.saleem792 akeerthi ap bfulgham simon.fraser zalan oldest_to_newest 1075563 0 webkit 2015-03-09 03:36:29 -0700 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 1092442 1 252551 webkit 2015-05-06 18:30:56 -0700 Created attachment 252551 Copy of JS Fiddle example 1110357 2 webkit 2015-07-18 01:51:56 -0700 Also filed a Radar for this: <rdar://problem/20090003> 1162793 3 webkit 2016-02-07 15:57:26 -0800 Still reproduces in Safari 9.0.3 1894749 4 ahmad.saleem792 2022-08-30 02:11:35 -0700 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! 1894917 5 ap 2022-08-30 14:03:46 -0700 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. 252551 2015-05-06 18:30:56 -0700 2015-05-06 18:30:56 -0700 Copy of JS Fiddle example example-2matzLja-1.html text/html 700 webkit PCFET0NUWVBFIGh0bWw+CjxodG1sPgo8aGVhZD4KICA8bWV0YSBodHRwLWVxdWl2PSJjb250ZW50 LXR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD1VVEYtOCI+CiAgPHRpdGxlPiAtIGpz RmlkZGxlIGRlbW88L3RpdGxlPgoKPHNjcmlwdD4Kd2luZG93Lm9ubG9hZCA9IGZ1bmN0aW9uICgp IHsKICBmdW5jdGlvbiBvbkRibENsaWNrKGUpIHsKICAgIHRoaXMucmVhZE9ubHkgPSBmYWxzZTsK ICAgIGNvbnNvbGUubG9nKCJkb3VibGUgY2xpY2tlZCIpOwogIH0KCiAgZnVuY3Rpb24gb25CbHVy KGUpIHsKICAgIHRoaXMucmVhZE9ubHkgPSB0cnVlOwogIH0KCiAgdmFyIGlucHV0MSA9IGRvY3Vt ZW50LmdldEVsZW1lbnRCeUlkKCdpbnB1dDEnKTsKICBpbnB1dDEuYWRkRXZlbnRMaXN0ZW5lcign ZGJsY2xpY2snLCBvbkRibENsaWNrKTsKICBpbnB1dDEuYWRkRXZlbnRMaXN0ZW5lcignYmx1cics IG9uQmx1cik7Cn0KCjwvc2NyaXB0PgoKCjwvaGVhZD4KPGJvZHk+CiAgPGRpdiBzdHlsZT0ibWFy Z2luOjVweDsiPgogICAgPHA+RG91YmxlLWNsaWNrIHRvIG1ha2Ugd3JpdGFibGUgKDxzdHJvbmc+ Y3Vyc29yIGxvc3Q8L3N0cm9uZz4gYnV0IHlvdSBzdGlsbCBjYW4gdHlwZSk8L3A+CiAgICA8aW5w dXQgaWQ9ImlucHV0MSIgdHlwZT0idGV4dCIgcmVhZG9ubHk9InJlYWRvbmx5Ij4KICA8L2Rpdj4K PC9ib2R5Pgo8L2h0bWw+Cg==