Open Bug 1940377 Opened 1 month ago Updated 1 day ago

Make `WhiteSpaceVisiblityKeeper` use an NBSP instead of collapsible ASCII white-space when it's the last character before a block boundary

Categories

(Core :: DOM: Editor, defect)

defect

Tracking

()

ASSIGNED

People

(Reporter: masayuki, Assigned: masayuki)

References

(Depends on 4 open bugs, Blocks 4 open bugs)

Details

(Keywords: parity-chrome, parity-safari)

When you type a white-space at end of a paragraph or the editing host in contenteditable=true whose white-space is normal, nowrap or pre-line, Gecko puts an ASCII white-space (U+0020) and a padding <br>. On the other hand, the other browsers puts an NBSP (U+00A0) without a padding <br>. When it becomes not the last character, Gecko just removes the padding <br>, but the other browsers replaces the NBSP with an ASCII white-space.

The root cause of bug 1925038, bug 1940278 and bug 1938110 is this bug.

Bug 1940278 and bug 1938110 avoids the regressions with hacky patch, but they may break some other web apps in some edge cases. Therefore, I think that we should give this really high priority.

htsai: I think that I should work on this in Q1 with the highest priority. WDYT?

Ideally, we should fix bug 1658699 first, but it may require to work on a lot of edge cases. So, I think that we should fix this without the complete fix of bug 1658699. Only the requirement is, working the white-spaces without major problem.

(So, the ideal goal here is, we fix this bug in 136.)

Severity: -- → S3

Okay, I'll enable the new normalizer with adding the code for inserting content.

Assignee: nobody → masayuki
Status: NEW → ASSIGNED
No longer depends on: 1940862, 1940874
OS: Unspecified → All
Hardware: Unspecified → All

Okay, I finished writing a patch for inserting text. It seems that I'll finish this faster than I've expected.

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