The attached file has your SVG example.

In DevTools on a Mac if I change the coordinates to push the curve to the right, it is still visible.

Please provide us with a more thorough reproduction case, with the event handlers etc. that replicate your situation.

Deleted: cr899291.html 926 bytes

cr899291.html 926 bytes View Download

Hi, thank you for your answer.
I prepare for you simple script. Try to move red point.
http://g.recordit.co/pz0CuShmfN.gif
Problem is when container has backface-visibility:hidden; and I modify bezier curve point.
You can reproduce it by using devtools as well http://g.recordit.co/6KI3c4qR7N.gif
It's working correctly on firefox, safari and chrome 69.

Deleted: index.html 2.6 KB

index.html 2.6 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

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

Bisected to r582337 = 46520ae13478333fe882e79041b667e5a3112796 = https://crrev.com/c/1168142 by chrishtr@chromium.org
"[PE] Stop dirtying compositing inputs on any layout for the root PaintLayer."
Landed in 70.0.3519.0

r.hilscher@ Thanks for the issue.

Able to reproduce this issue on Windows 10, Mac OS 10.13.6 and Ubuntu 17.10 on the reported version 71.0.3578.20 and latest Canary 72.0.3595.0.

Bisect Information:
===================
Good Build: 70.0.3518.0
Bad Build : 70.0.3519.0

As per comment #4, suspecting the below change:
Reviewed-on: https://chromium-review.googlesource.com/1168142

chrishtr@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.

Adding 'ReleaseBlock-Stable' as this is a recent regression. Please feel free to remove if it is not applicable.

Thanks..

Confirmed still broken in Canary (M-72) and Beta (M-71), so not fixed by anything else.

M71 Stable promotion is coming VERY soon. Your bug is labelled as Stable  ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Thank you.

M71 Stable promotion is coming VERY soon. Your bug is labelled as Stable  ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Thank you.

Vlad, I'm not sure Chris will be back in time for the stable promotion. Could you look at this?

Hi. I believe I'm facing the same overflow issue on Chrome 70. To reproduce the problem, click on "Extend Line" button in the attached test page. The expected and actual results are attached as screenshots.

Note that the SVG element in the test page has overflow, will-change and transform properties applied.

Deleted: svg-overflow-bug-chrome70.html 1.0 KB

svg-overflow-bug-chrome70.html 1.0 KB View Download

Deleted: expected.png 22.9 KB

	expected.png 22.9 KB View Download

Deleted: actual.png 19.4 KB

	actual.png 19.4 KB View Download

Yep that looks like the same issue. The fix is in cq

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/29b5904fa94cfcc838990f2cc731662a79979c46

commit 29b5904fa94cfcc838990f2cc731662a79979c46
Author: Vladimir Levin <vmpstr@chromium.org>
Date: Tue Oct 30 01:38:07 2018

Ensure to invalidate compositing inputs on svg overflow change.

This patch ensures that we dirty the compositing inputs if our svg root
has visible overflow and that overflow changes.

R=chrishtr@chromium.org, pdr@chromium.org

Bug:  899291 
Change-Id: Iaaa0eb7f48b9855af141e6b3d79d3a1667c6e38f
Reviewed-on: https://chromium-review.googlesource.com/c/1306408
Commit-Queue: vmpstr <vmpstr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#603725}
[modify] https://crrev.com/29b5904fa94cfcc838990f2cc731662a79979c46/third_party/blink/renderer/core/layout/svg/layout_svg_root.cc
[modify] https://crrev.com/29b5904fa94cfcc838990f2cc731662a79979c46/third_party/blink/renderer/core/layout/svg/layout_svg_root_test.cc

Our customers rely on this fix for their graphics editing workflows to work properly. Any chance the fix can make it into Stable v70 or is that impossible?

The fix is definitely a good release merge candidate.

We'll let this sit in Canary for a day then request merge back to M-71 Beta, then if that goes well we'll discuss M-70 Stable. It's unlikely we will release a Stable update just for this, so we will need to coordinate with the release managers to find out what other issues might cause a Stable revision.

CL listed at #15 is not in canary yet. Pls update bug with canary result tomorrow. If change looks good in canary, will approve merge to M71. Thank you.

This bug requires manual review: M71 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: benmason@(Android), kariahda@(iOS), kbleicher@(ChromeOS), govind@(Desktop)

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

@#18, the fix is pretty safe, so I'm comfortable with the merge whenever it is approved. I'll update the bug if there are any Canary issues that surface, but all else being quiet, I'd say we can merge.

The NextAction date has arrived: 2018-10-31

Approving merge to M71 branch 3578 based on comment #20 and per offline with pdr@.

The following revision refers to this bug: 
https://chromium.googlesource.com/chromium/src.git/+/3075c459af7d475892d868fcfd430fabc6fab42d

Commit: 3075c459af7d475892d868fcfd430fabc6fab42d
Author: vmpstr@chromium.org
Commiter: vmpstr@chromium.org
Date: 2018-10-31 20:58:55 +0000 UTC

Ensure to invalidate compositing inputs on svg overflow change.

This patch ensures that we dirty the compositing inputs if our svg root
has visible overflow and that overflow changes.

R=chrishtr@chromium.org, pdr@chromium.org
TBR=vmpstr@chromium.org

(cherry picked from commit 29b5904fa94cfcc838990f2cc731662a79979c46)

Bug:  899291 
Change-Id: Iaaa0eb7f48b9855af141e6b3d79d3a1667c6e38f
Reviewed-on: https://chromium-review.googlesource.com/c/1306408
Commit-Queue: vmpstr <vmpstr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#603725}
Reviewed-on: https://chromium-review.googlesource.com/c/1311088
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/branch-heads/3578@{#438}
Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3075c459af7d475892d868fcfd430fabc6fab42d

commit 3075c459af7d475892d868fcfd430fabc6fab42d
Author: Vladimir Levin <vmpstr@chromium.org>
Date: Wed Oct 31 20:58:55 2018

Ensure to invalidate compositing inputs on svg overflow change.

This patch ensures that we dirty the compositing inputs if our svg root
has visible overflow and that overflow changes.

R=chrishtr@chromium.org, pdr@chromium.org
TBR=vmpstr@chromium.org

(cherry picked from commit 29b5904fa94cfcc838990f2cc731662a79979c46)

Bug:  899291 
Change-Id: Iaaa0eb7f48b9855af141e6b3d79d3a1667c6e38f
Reviewed-on: https://chromium-review.googlesource.com/c/1306408
Commit-Queue: vmpstr <vmpstr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#603725}
Reviewed-on: https://chromium-review.googlesource.com/c/1311088
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/branch-heads/3578@{#438}
Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}
[modify] https://crrev.com/3075c459af7d475892d868fcfd430fabc6fab42d/third_party/blink/renderer/core/layout/svg/layout_svg_root.cc
[modify] https://crrev.com/3075c459af7d475892d868fcfd430fabc6fab42d/third_party/blink/renderer/core/layout/svg/layout_svg_root_test.cc

I'm not able to reproduce the issue described in comment #13 in Canary Version 72.0.3598.0.

Looking forward to seeing this fix in the upcoming M71, and hopefully the stable M70 if possible.

Is there an ETA for when the fix will be merged to M71?

I'm not able to reproduce the issue described in comment #13 in Chrome Beta Version 71.0.3578.44.