Here is a replica on jsbin without all the iframe cruft.

http://output.jsbin.com/yujuyoxeca

marakow@ was this causing a real issue for something? Just want to make sure we set the priority correctly; as it is likely getting into a subtle difference in the code somewhere treating the layer as a plain layer and not a layer with a stacking context.

Layout tree is:

out/Release/content_shell --run-layout-test http://output.jsbin.com/yujuyoxeca
#READY
Content-Type: text/plain
layer at (0,0) size 800x600
  LayoutView at (0,0) size 800x600
layer at (0,0) size 800x600
  LayoutBlockFlow {HTML} at (0,0) size 800x600
    LayoutBlockFlow {BODY} at (8,8) size 784x584
      LayoutBlockFlow (anonymous) at (0,0) size 784x20
        LayoutText {#text} at (0,0) size 148x19
          text run at (0,0) width 148: "Click the element below."
layer at (8,28) size 200x200
  LayoutBlockFlow {DIV} at (0,20) size 200x200 [bgcolor=#FF0000]
layer at (8,28) size 200x200
  LayoutBlockFlow {DIV} at (0,0) size 200x200 [bgcolor=#00FFFF]
layer at (8,28) size 200x200
  LayoutBlockFlow {DIV} at (0,0) size 200x200 [bgcolor=#008000]
layer at (685,0) size 110x31
  LayoutBlockFlow (positioned) {A} at (685,0) size 110x31 [color=#777777] [bgcolor=#DDDDDD] [border: none (1px solid #999999)]
    LayoutText {#text} at (10,7) size 75x15
      text run at (10,7) width 75: "Edit in JS Bin "
    LayoutImage {IMG} at (88,6) size 16x16
#EOF
#EOF
#EOF

Moving Blink>Input>HitTesting to Blink>HitTesting

Marking available, as I assume you're not working on a fix.

Safari's behavior matches Chrome.

Firefox works as comment 0 expects.

It appears Chrome simply doesn't have support for hit-testing in 3D. see method
isHitCandidate in PaintLayer.cpp:


// The hit layer is depth-sorting with other layers, so just say that it was
// hit.
if (canDepthSort)
   return true;

And per comment 0, Edge matches Firefox.

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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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