164510 2016-11-08 02:43:12 -0800 text-combine-upright should ignore forced line breaks 2023-05-22 09:10:45 -0700 1 1 1 Unclassified WebKit Layout and Rendering Safari 10 Unspecified Unspecified RESOLVED CONFIGURATION CHANGED FromImplementor, InRadar P2 Normal --- 150821 1 kojii webkit-unassigned ahmad.saleem792 mmaxfield ntim simon.fraser webkit-bug-importer zalan oldest_to_newest 1249016 0 kojii 2016-11-08 02:43:12 -0800 The spec 9.1.2. Layout Rules defines "ignoring ... any forced line breaks". https://drafts.csswg.org/css-writing-modes-3/#text-combine-layout STEPS: 1. Open http://test.csswg.org/harness/test/css-writing-modes-3_dev/single/text-combine-upright-break-inside-001a/format/html5/ EXPECTED: Test should render the same as "Reference Page" tab. Note that since the test does not have prefix, you will need to add one, or use bookmarklets <http://kojiishi.github.io/tweak-css-tests/> to reproduce. chrome bug: http://crbug.com/663308 1249327 1 webkit-bug-importer 2016-11-09 10:34:44 -0800 <rdar://problem/29181797> 1907619 2 ntim 2022-10-23 00:41:01 -0700 *** Bug 234761 has been marked as a duplicate of this bug. *** 1907620 3 ntim 2022-10-23 00:42:00 -0700 imported/w3c/web-platform-tests/css/css-writing-modes/text-combine-upright-break-inside-001.html [ ImageOnlyFailure ] imported/w3c/web-platform-tests/css/css-writing-modes/text-combine-upright-break-inside-001a.html [ ImageOnlyFailure ] 1956951 4 ahmad.saleem792 2023-05-22 08:15:33 -0700 (In reply to Tim Nguyen (:ntim) from comment #3) > imported/w3c/web-platform-tests/css/css-writing-modes/text-combine-upright- > break-inside-001.html [ ImageOnlyFailure ] > imported/w3c/web-platform-tests/css/css-writing-modes/text-combine-upright- > break-inside-001a.html [ ImageOnlyFailure ] We are passing these tests on STP170. https://wpt.fyi/results/css/css-writing-modes?label=master&label=experimental&aligned&q=text-combine-upright-break-inside ^ Do we need to do anything else? I think we can mark this as fixed. 1956957 5 ntim 2023-05-22 08:44:39 -0700 Looks like this was fixed by some IFC change. 1956967 6 zalan 2023-05-22 09:10:45 -0700 (In reply to Tim Nguyen (:ntim) from comment #5) > Looks like this was fixed by some IFC change. Correct, these have progressed at 257036@main when text-combine content got enabled for IFC (tagging with IFC progression).