New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 760464 link

Starred by 4 users
Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
█ manoranj...@chromium.org
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

wrong size of <td> with <ruby> in <table>

Reported by odd.ubu...@gmail.com, Aug 30 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/59.0.3071.109 Chrome/59.0.3071.109 Safari/537.36

Steps to reproduce the problem:
以下に示すソースコードを表示する。
View source showed below.

~~~

<html>
<head>
</head>
<body>
<table>
    <tbody>
        <tr>
            <td style="width:100px; border:1px solid;"><ruby><rb>漢字</rb><rt>ふりがな</rt></ruby></td>
            <td style="width:100px; border:1px solid;">ああああああああああああ</td>
        </tr>
        <tr>
            <td style="width:100px; border:1px solid;"><ruby><rb>漢字2</rb><rt>ふりがな2</rt></ruby>ああああああああああああ</td>
            <td style="width:100px; border:1px solid;">あああ</td>
        </tr>
        <tr>
            <td style="width:100px; border:1px solid;">a</td>
            <td style="width:100px; border:1px solid;">a</td>
        </tr>
    </tbody>
</table>
</body>
</html>

~~~

What is the expected behavior?

What went wrong?
td要素の大きさがおかしい。
size of td is wrong.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 59.0.3071.109  Channel: n/a
OS Version: 
Flash Version:
Screenshot from 2017-08-30 16-02-34.png
53.1 KB View Download
Screenshot from 2017-08-30 15-59-22.png
23.1 KB View Download
2017-08-30 15.54.10.png
52.1 KB View Download

Comment 1 by manoranj...@chromium.org, Aug 30 2017

Labels: Needs-Feedback
odd.ubuntu@, The latest chrome stable is #60.0.3112.113, can you please update to latest chrome through chrome://chrome and see if it still reproduces?

Thank you!

Comment 2 by odd.ubu...@gmail.com, Aug 31 2017 

thanks.
i upgraded Chromium and retried. but not been fixed ...
Screenshot from 2017-08-31 09-31-24.png
29.3 KB View Download
Screenshot from 2017-08-31 09-31-12.png
32.4 KB View Download
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 31 2017

Cc: manoranj...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "manoranjanr@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 Deleted

Comment 5 by odd.ubu...@gmail.com, Aug 31 2017 

In addition, I tried in Chrome(or Chromium) in some OS.

- Linux(Ubuntu 16.04)
- Linux(Android 7.1)
- Windows(Windows 10)

This bug reproduce in all.

Comment 6 by brajkumar@chromium.org, Aug 31 2017

Cc: brajkumar@chromium.org
Labels: Needs-Triage-M60 Needs-Feedback
Tested this issue on Ubuntu 14.04 using chrome latest stable #60.0.3112.113 using the test case provided in the original comment. Observed similar behavior as shown in the second screen shot of the original comment.

Reporter@ If the above behavior is not the expected one, could you please provide any sample screen shot of the expected behavior of this issue? Does this issue used to work before in chrome? Tested the same on firefox but the texts are not rendered properly.

Thanks!

Comment 7 by odd.ubu...@gmail.com, Aug 31 2017 

Attach file of this comment is screenshot in Firefox.
Border lines are neatly aligned.

Thanks.
Screenshot from 2017-08-31 20-21-47.png
13.3 KB View Download
Project Member

Comment 8 by sheriffbot@chromium.org, Aug 31 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 by tkent@chromium.org, Sep 1 2017

Components: -Blink>HTML Blink>Layout

Comment 10 by e...@chromium.org, Sep 1 2017

Status: WontFix (was: Unconfirmed)
We're planning to redo our ruby support next year as our current implementation is rather lacking. Realistically we're not going to be able to fix this until then I'm afraid.
►

Sign in to add a comment