Bug 166685

Summary: Caret is incorrectly aligned in empty table cells inside a contenteditable region
Product: WebKit Reporter: Manuel Rego Casasnovas <rego>
Component: Layout and RenderingAssignee: Manuel Rego Casasnovas <rego>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: clopez, simon.fraser
Priority: P2 Keywords: BlinkMergeCandidate
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.chromium.org/p/chromium/issues/detail?id=421716
Attachments:
Description Flags
Example to reproduce the issue
none
Current output
none
Expected output none

Manuel Rego Casasnovas
Reported 2017-01-04 07:46:29 PST
Created attachment 298010 [details] Example to reproduce the issue The caret is not properly aligned in an empty table cell when the table is inside a contenteditable region. Check the attached example to see the issue. When you click on the empty cell you'll see that the caret is outside the cell, when you start to type the issue is fixed. As a workaround you can add an empty space (&nbsp;) or use "vertical-align: top;" to avoid the issue.
Attachments
Example to reproduce the issue (521 bytes, text/html)
2017-01-04 07:46 PST, Manuel Rego Casasnovas 		no flags
Details
Current output (19.79 KB, image/png)
2017-01-04 07:46 PST, Manuel Rego Casasnovas 		no flags
Details
Expected output (19.74 KB, image/png)
2017-01-04 07:47 PST, Manuel Rego Casasnovas 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Manuel Rego Casasnovas
Comment 1 2017-01-04 07:46:57 PST
Created attachment 298011 [details] Current output
Manuel Rego Casasnovas
Comment 2 2017-01-04 07:47:23 PST
Created attachment 298012 [details] Expected output
Manuel Rego Casasnovas
Comment 3 2017-01-04 07:52:47 PST
This has been recently fixed in Blink: https://codereview.chromium.org/2601923003
Manuel Rego Casasnovas
Comment 4 2017-01-04 07:54:22 PST
Ups, I've just realized this was already reported in bug #85385. *** This bug has been marked as a duplicate of bug 85385 ***
Note You need to log in before you can comment on or make changes to this bug.