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

Issue 632927 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Chrome .offsetHeight on <br> returns 0, doesn't match getBoundingClientRect().height

Reported by bbri...@microsoft.com, Jul 30 2016

Issue description

OS: it's not XP

What steps will reproduce the problem?
(1) https://jsfiddle.net/rwty0pbn/

What is the expected output?

Not a zero, same value as other APIs

What do you see instead?

Chrome:
0 for offsetHeight, 17 for gBCR.height

Firefox:
19 for both

Edge:
18 offsetHeight, 18.39 for gBCR.height

Note: We found this while investigating CKEditor interop issue on lego.com site

 

Comment 1 by e...@chromium.org, Aug 1 2016

Status: Available (was: Untriaged)
Can I take this?

Comment 3 by e...@chromium.org, Aug 2 2016

This is because LayoutBR inherits from LayoutText rather than LayoutBoxModelObject and thus doesn't have the offsetHeight method.

Comment 4 by e...@chromium.org, Aug 2 2016

Cc: hyungwoo...@navercorp.com
Sure hyungwook.lee, it's all yours.

HTMLElement::offsetHeightForBinding in HTMLElement.cpp is the method that gets called when invoking element.offsetHeight.
So, we should make LayoutBR inherit from LayoutBoxModelObject or just try to fix it by computing the height differently in offsetHeightForBinding
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 12 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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

Comment 7 by e...@chromium.org, Apr 18 2018

Status: Fixed (was: Untriaged)
Fixed in LayoutNG. We won't get around to fix it in legacy layout.

Sign in to add a comment