New issue
Advanced search Search tips

Issue 859497 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Jan 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task



Sign in to add a comment

[LayoutNG] Inline fragmentation in bidi is not implemented yet

Project Member Reported by mstensho@chromium.org, Jul 2

Issue description

I don't know much about bidi, so I can't tell what's right and wrong here, but we do differ from legacy layout (see test case), and the only thing preventing us from failing fast/borders/bidi-009a.html is that we currently fall back to legacy layout due to an anonymous table-cell (I'm in the process of fixing that).

The test attached is based on that test.

From the looks of it, fast/borders/bidi-002.html also fails because of this bug.

I hope someone with more knowledge can update the bug summary with a better title. :)
 
tc.html
116 bytes View Download
Summary: [LayoutNG] Inline fragmentation in bidi is not implemented yet (was: [LayoutNG] Bidi problem)
Thank you for filing this, yeah, this is not-implemented-yet, on my backlog.

Bidi reordering may fragment an inline box to multiple fragments within a line. Our current LayoutNG implementation creates a single inline box of a united bounds instead.
Looks like https://chromium-review.googlesource.com/c/1323989 implemented inline fragmentation in bidi, and fixed the failing tests. Do you still want to keep this bug open?
Labels: -Type-Bug Type-Task
Status: Fixed (was: Available)
Right, forgot we have this bug. Thank you for the notice.

Sign in to add a comment