christhtr@, which bug is this duplicate of?

I think this is the reason we raised https://github.com/w3c/svgwg/issues/427

...actually, scratch that. I thought this might've been something about event transparency, but looking at the TC it does look like it. So probably  issue 842668 ?

A bit more info on this bug. The presence of a foreignObject anywhere in an svg stops document.elementsFromPoint from reporting any other svg element in the svg except the oldest foreignObject present in the svg when it is clicked. See the attached test file.

1. Click on the left blue circle and only the first foreignObject is reported in the console
2. Click the right blue circle, no foreignObject or circle or rect are reported
3. Click "Remove ForeignObject" button (this removes the foreignObject on the left)
4. Click the right blue circle and now the second foreignObject is reported, but nothing else in the SVG
5. Click "Remove ForeignObject" button again (this removes the second foreignObject, no foreignObjects are left in the svg)
6. Click any part of the svg and what is reported by elementsFromPoint is now as expected

Tested in 67.0.3396.79 and 69.0.3451.0

Deleted: svg-foreignobject.html 1.8 KB

svg-foreignobject.html 1.8 KB View Download

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

commit 31c3829005a8bd2f699eb61d565a0da2dd855d01
Author: Fredrik Söderquist <fs@opera.com>
Date: Tue Jun 12 11:52:55 2018

Don't corrupt list-based hit-test results in LayoutSVGForeignObject

Assigning the HitTestResult used for the PaintLayer will corrupt (reset)
any result acquired previously. So results from the foreground phase
would be erased by any later phase(s). Use HitTestResult::Append
instead if we're performing a list-based hit-test.

Bug:  849617 
Change-Id: I5f53cad7e8396377815af51bd52db924b3fe6d5a
Reviewed-on: https://chromium-review.googlesource.com/1095182
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566382}
[modify] https://crrev.com/31c3829005a8bd2f699eb61d565a0da2dd855d01/third_party/WebKit/LayoutTests/fast/dom/elementsFromPoint/elementsFromPoint-svg-expected.txt
[modify] https://crrev.com/31c3829005a8bd2f699eb61d565a0da2dd855d01/third_party/WebKit/LayoutTests/fast/dom/elementsFromPoint/elementsFromPoint-svg.html
[modify] https://crrev.com/31c3829005a8bd2f699eb61d565a0da2dd855d01/third_party/blink/renderer/core/layout/svg/layout_svg_foreign_object.cc

Thanks for fixing promptly, it is much appreciated.

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

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

Let's target the fix for M69, since this bug has been present in M66 and M67. We're already post branch for 68.