267887 2024-01-22 15:56:58 -0800 WebKit is missing UA stylesheet rule to apply 'unicode-bidi: isolate' to div elements 2024-01-22 16:47:15 -0800 1 1 1 Unclassified WebKit CSS Safari 17 Unspecified Unspecified RESOLVED DUPLICATE 65617 https://bugs.chromium.org/p/chromium/issues/detail?id=1520671 https://bugs.webkit.org/show_bug.cgi?id=65617 https://bugzilla.mozilla.org/attachment.cgi?id=9375895 BrowserCompat P2 Normal --- 1 dholbert webkit-unassigned ahmad.saleem792 darin heycam ntim oldest_to_newest 2006705 0 dholbert 2024-01-22 15:56:58 -0800 STR: 1. Load https://bugzilla.mozilla.org/attachment.cgi?id=9375895 EXPECTED RESULTS: The bold part of the testcase should say: 'isolate' (as expected) ACTUAL RESULTS: The bold part of the testcase says: 'normal' UNEXPECTED This testcase is just highlighting that WebKit seems to be lacking one of the UA stylesheet rules that the html spec requires here: https://html.spec.whatwg.org/multipage/rendering.html#bidi-rendering Quoting the rule (note 'div' is the 4th element in the selector list): ``` address, blockquote, center, div, figure, figcaption, footer, form, header, hr, legend, listing, main, p, plaintext, pre, summary, xmp, article, aside, h1, h2, h3, h4, h5, h6, hgroup, nav, section, search, table, caption, colgroup, col, thead, tbody, tfoot, tr, td, th, dir, dd, dl, dt, menu, ol, ul, li, bdi, output, slot, [dir=ltr i], [dir=rtl i], [dir=auto i] { unicode-bidi: isolate; } ``` Firefox gives the expected result. (Chromium also gives ACTUAL RESULTS here; I filed https://bugs.chromium.org/p/chromium/issues/detail?id=1520671 on them.) 2006708 1 dholbert 2024-01-22 15:59:57 -0800 I tested Safari Version 17.0 (19616.1.27.211.1) on macOS Sonoma, FWIW. 2006711 2 ahmad.saleem792 2024-01-22 16:05:47 -0800 I think @noam tried to do it in another bug 65617 by importing the UA Stylesheet rule and then Darin had feedback to do it where we explicitly set 'display: block' and other remaining in block. Darin's feedback - https://bugs.webkit.org/show_bug.cgi?id=65617#c18 I had this rule in my local build as well to look into test failures and others bit and noticed that it would take some time to fix them, so didn't did the PR but I think we should do this change. 2006714 3 darin 2024-01-22 16:12:26 -0800 *** This bug has been marked as a duplicate of bug 65617 *** 2006731 4 dholbert 2024-01-22 16:47:15 -0800 Thanks! Glad this is a known/agreed-upon issue.