Bug 156399 - Textarea multiline placeholder not restored fully until element blurred
Summary: Textarea multiline placeholder not restored fully until element blurred
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: Safari 9
Hardware: Mac OS X 10.11
: P2 Normal
Assignee: Nobody
URL: http://codepen.io/jrencz/pen/oxpqoj
Keywords: EasyFix, InRadar
: 216321 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-04-08 02:28 PDT by Jarek Rencz
Modified: 2022-01-19 15:31 PST (History)
9 users (show)

See Also:


Attachments
As seen on Safari 9.0.3 (35.96 KB, image/png)
2016-04-08 02:28 PDT, Jarek Rencz
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jarek Rencz 2016-04-08 02:28:20 PDT
Created attachment 275987 [details]
As seen on Safari 9.0.3

When a textarea is rendered initially below the fold (below 100vh from the top of the page) the placeholder is not restored fully after some text is put in and then removed until element is blurred.

Demo:
http://codepen.io/jrencz/pen/oxpqoj

Confirmed to be reproducible in:
Safari 9.0.3
Safari 9.1
Safari TP
Webkit Nightly r199217
Comment 1 Michał Gołębiowski-Owczarek 2016-04-08 02:30:09 PDT
I can reproduce it as well on OS X 10.11.4 in Safari 9.1.
Comment 2 Damian Wielgosik 2016-04-08 02:49:15 PDT
I could fix it by forcing the layout trashing when element's content is empty: http://codepen.io/varjs/pen/JXMvoR
Comment 3 Ben Creasy 2017-07-18 00:49:06 PDT
Any activity around this?
Comment 4 Radar WebKit Bug Importer 2017-07-18 08:54:37 PDT
<rdar://problem/33377050>
Comment 5 Alexey Proskuryakov 2020-09-09 15:26:50 PDT
*** Bug 216321 has been marked as a duplicate of this bug. ***
Comment 6 asefkow 2020-09-09 21:46:12 PDT
Bug 216321 has a very small attached HTML file that clearly demonstrates the problem, which is still reproducing in Safari 13.1.2.
Comment 7 Chris Dumez 2022-01-19 15:31:48 PST
Cannot reproduce the issue on shipping Safari. Tried both the test attached to Bug 216321 and http://codepen.io/jrencz/pen/oxpqoj (from this bug).

I believe this was fixed.