Bug 156399

Summary:

Textarea multiline placeholder not restored fully until element blurred

Product:

WebKit

Reporter:

Jarek Rencz <jaroslaw>

Component:

Forms

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED FIXED

Severity:

Normal

CC:

asefkow, cdumez, damian.wielgosik, jaroslaw, m.goleb+bugzilla, pxlcoder, simon.fraser, webkit-bug-importer, zalan

Priority:

Keywords:

EasyFix, InRadar

Version:

Safari 9

Hardware:

Mac

OS:

OS X 10.11

URL:

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

Attachments:

Description	Flags
As seen on Safari 9.0.3	none

Jarek Rencz

Reported 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

Attachments
As seen on Safari 9.0.3 (35.96 KB, image/png) 2016-04-08 02:28 PDT, Jarek Rencz	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Michał Gołębiowski-Owczarek

Comment 1 2016-04-08 02:30:09 PDT

I can reproduce it as well on OS X 10.11.4 in Safari 9.1.

Damian Wielgosik

Comment 2 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

Ben Creasy

Comment 3 2017-07-18 00:49:06 PDT

Any activity around this?

Radar WebKit Bug Importer

Comment 4 2017-07-18 08:54:37 PDT

<rdar://problem/33377050>

Alexey Proskuryakov

Comment 5 2020-09-09 15:26:50 PDT

*** Bug 216321 has been marked as a duplicate of this bug. ***

asefkow

Comment 6 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.

Chris Dumez

Comment 7 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.

Note You need to log in before you can comment on or make changes to this bug.