RESOLVED CONFIGURATION CHANGED 91588
Japanese line breaking rule doesn't work if target character is adjacent to ruby characters
https://bugs.webkit.org/show_bug.cgi?id=91588
Summary Japanese line breaking rule doesn't work if target character is adjacent to r...
Tatsuya Nitta
Reported 2012-07-17 23:44:12 PDT
Created attachment 152940 [details] Test HTML file to reproduce the issue Overview: If Japanese characters with ruby are adjacent to the target character and the target character is prohibited to place at the end of line or the beginning of the line, the target character can be placed at the prohibited position. Steps to Reproduce: 1) Open the attached test file which contains ruby characters("直帰") being adjacent to character("「") which is prohibited to place at the end of line 2) Drag the resizable corner to resize the window in order to position the character at the end of line 3) Compare the result between the case of characters with ruby and without ruby Actual Results: When the target chararcter is adjacent to characters with ruby, line breaking occurs after the character which is prohibited to place at the end of line, or occurs before the character which is prohibited to place at the beginning of line. Expected Results: No matter if character is adjacent to characters with ruby, Japanese line breaking rule should work. Additional Information: This occurs no matter what writing direction is, like vertical and horizontal.
Attachments
Test HTML file to reproduce the issue (891 bytes, text/html)
2012-07-17 23:44 PDT, Tatsuya Nitta
no flags
Screenshot of result in webkit (80.45 KB, image/png)
2012-07-17 23:45 PDT, Tatsuya Nitta
no flags
Test HTML file to reproduce the issue (1.04 KB, text/html)
2012-07-19 21:12 PDT, Tatsuya Nitta
no flags
Patch (64.86 KB, patch)
2012-12-11 17:40 PST, Yuki Sekiguchi
no flags
Rebase (64.38 KB, patch)
2012-12-17 18:39 PST, Yuki Sekiguchi
no flags
Patch (18.71 KB, patch)
2015-01-20 11:55 PST, Dave Hyatt
dino: review+
Tatsuya Nitta
Comment 1 2012-07-17 23:45:09 PDT
Created attachment 152942 [details] Screenshot of result in webkit
Tatsuya Nitta
Comment 2 2012-07-19 21:12:08 PDT
Created attachment 153394 [details] Test HTML file to reproduce the issue
Tatsuya Nitta
Comment 3 2012-10-12 00:51:00 PDT
It's been a while since I logged this bug. It seems there is no update. Can someone look at this issue?
mitz
Comment 4 2012-10-12 01:10:56 PDT
Dan Song
Comment 5 2012-10-16 01:38:03 PDT
Only occurred on Mac
Dan Song
Comment 6 2012-10-16 01:45:30 PDT
(In reply to comment #5) > Only occurred on Mac Sorry that please ignore this.
Yuki Sekiguchi
Comment 7 2012-12-11 16:21:15 PST
*** Bug 104645 has been marked as a duplicate of this bug. ***
Yuki Sekiguchi
Comment 8 2012-12-11 17:40:50 PST
Yuki Sekiguchi
Comment 9 2012-12-17 18:39:49 PST
Anders Carlsson
Comment 10 2014-02-05 11:01:57 PST
Comment on attachment 179852 [details] Rebase Clearing review flag on patches from before 2014. If this patch is still relevant, please reset the r? flag.
Dave Hyatt
Comment 11 2015-01-20 11:55:34 PST
WebKit Commit Bot
Comment 12 2015-01-20 11:57:00 PST
Attachment 245006 [details] did not pass style-queue: ERROR: Source/WebCore/rendering/RenderBlockFlow.h:461: Missing space inside { }. [whitespace/braces] [5] ERROR: Source/WebCore/rendering/RenderRubyText.h:50: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Total errors found: 2 in 17 files If any of these errors are false positives, please file a bug against check-webkit-style.
Koji Ishii
Comment 13 2015-01-20 19:27:15 PST
Koji Ishii
Comment 14 2015-01-22 04:56:58 PST
Update: Gecko revised their thoughts and trying to follow the spec. As long as impl are happy, there's no reasons to change the spec. http://lists.w3.org/Archives/Public/www-style/2015Jan/0403.html
Jon Lee
Comment 15 2015-01-23 09:11:17 PST
Koji Ishii
Comment 16 2015-08-23 19:21:07 PDT
In porting the fix to Blink http://crbug.com/522826, it looks like RenderRubyText::canBreakBefore() checks "prohibit break before" for the previous characters, where it should check "prohibit break after", so it fails OP+ruby case. A test here (click "Test Case" tab to run): http://test.csswg.org/shepherd/testcase/line-break-around-ruby-001/name/line-break-around-ruby/
Ahmad Saleem
Comment 17 2023-05-25 14:15:14 PDT
(In reply to Koji Ishii from comment #16) > In porting the fix to Blink http://crbug.com/522826, it looks like > RenderRubyText::canBreakBefore() checks "prohibit break before" for the > previous characters, where it should check "prohibit break after", so it > fails OP+ruby case. > > A test here (click "Test Case" tab to run): > http://test.csswg.org/shepherd/testcase/line-break-around-ruby-001/name/line- > break-around-ruby/ This is also now on WPT. Blink / Chrome landed this commit: https://src.chromium.org/viewvc/blink?view=revision&revision=201073
Ahmad Saleem
Comment 18 2024-09-16 14:17:03 PDT
(In reply to Ahmad Saleem from comment #17) > (In reply to Koji Ishii from comment #16) > > In porting the fix to Blink http://crbug.com/522826, it looks like > > RenderRubyText::canBreakBefore() checks "prohibit break before" for the > > previous characters, where it should check "prohibit break after", so it > > fails OP+ruby case. > > > > A test here (click "Test Case" tab to run): > > http://test.csswg.org/shepherd/testcase/line-break-around-ruby-001/name/line- > > break-around-ruby/ > > This is also now on WPT. > > Blink / Chrome landed this commit: > https://src.chromium.org/viewvc/blink?view=revision&revision=201073 SVN is gone - https://github.com/chromium/chromium/commit/65c133764c0925fd7baabb58374574c43450b85f
alan
Comment 19 2024-09-16 14:23:14 PDT
IFC (ruby) progression (I remember adding support for it)
Note You need to log in before you can comment on or make changes to this bug.