Bug 166685 - Caret is incorrectly aligned in empty table cells inside a contenteditable region
Summary: Caret is incorrectly aligned in empty table cells inside a contenteditable re...
Status: RESOLVED DUPLICATE of bug 85385
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Manuel Rego Casasnovas
URL:
Keywords: BlinkMergeCandidate
Depends on:
Blocks:
 
Reported: 2017-01-04 07:46 PST by Manuel Rego Casasnovas
Modified: 2017-01-04 07:54 PST (History)
2 users (show)

See Also:

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 an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Manuel Rego Casasnovas 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 ( ) or use "vertical-align: top;" to avoid the issue.
Comment 1 Manuel Rego Casasnovas 2017-01-04 07:46:57 PST 
Created attachment 298011 [details]
Current output
Comment 2 Manuel Rego Casasnovas 2017-01-04 07:47:23 PST 
Created attachment 298012 [details]
Expected output
Comment 3 Manuel Rego Casasnovas 2017-01-04 07:52:47 PST 
This has been recently fixed in Blink:
https://codereview.chromium.org/2601923003
Comment 4 Manuel Rego Casasnovas 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 ***