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

Issue 801384 link

Starred by 1 user
Status: Duplicate
Merged: issue 771852
Owner: ----
Closed: Jan 2018
Cc:
█ trchen@chromium.org
chrishtr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 640272



Sign in to add a comment

Behavior of positioned object under SVG foreignObject

Project Member Reported by wangxianzhu@chromium.org, Jan 12 2018 
We are inconsistent in layout and paint. We treat foreignObject as the containing block of fixed and absolute positioned objects (https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/layout/LayoutBlock.cpp?rcl=16f761349c375d769a7ebd0525b50403ed832acb&l=255), but the offset and clip of foreignObject don't apply on the positioned object during painting. I think this is a result of our layer painting mechanism because foreignObject doesn't create layer.

Test case: http://jsbin.com/xeterap

Edge and Firefox consistently treat foreignObject as the containing block of all descendants. Safari behaves the same as Chrome.

The Edge/Firefox behavior can be easily implemented in Chrome in SPv175, but we need to be careful changing the behavior.

Comment 1 by chrishtr@chromium.org, Jan 12 2018 

Does creating a PaintLayer for it "Fix" the issue in terms of Firefox compat?

https://chromium-review.googlesource.com/c/chromium/src/+/831397

Comment 2 by wangxianzhu@chromium.org, Jan 12 2018 

Re #c1: Yes for SPv1 (with other issues). Doesn't matter for SPv175+ with https://chromium-review.googlesource.com/c/chromium/src/+/862284.

Haven't we already treated the current behavior as a bug (e.g.  bug 771852 )?

Comment 3 by wangxianzhu@chromium.org, Jan 12 2018 

I think the "Intent to Ship" https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/DHSUFGpZafc implies the Edge/Firefox behavior in this bug, right?

Comment 4 by chrishtr@chromium.org, Jan 12 2018 

Let's add this to the intent to ship then and do some quick compat analysis.

But the change will have to wait for SPv175, for the reasons explained in 
 issue 771852 .

Comment 5 by f...@opera.com, Jan 12 2018

Blocking: 640272

Comment 6 by wangxianzhu@chromium.org, Jan 12 2018

Mergedinto: 771852
Status: Duplicate (was: Available)
►

Sign in to add a comment