New issue
Advanced search Search tips

Issue 883355 link

Starred by 2 users
Status: WontFix
Owner:
szager@chromium.org
Closed: Sep 14
Cc:
ajha@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

IntersectionObserver seeing elements with opacity below 1 as Intersecting:true

Reported by arledgem...@gmail.com, Sep 12 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36

Steps to reproduce the problem:
1. Add opacity to children of container
2. Open devtools and see that 9 of 7 have been intersecting
3. Remove opacity to children of container
4. Open devtools and see that 7 of 9 (lol) elements are selected (as expected)

What is the expected behavior?
The expected behavior is that elements with opacity applied to them should not be counted is intersecting. 

What went wrong?
https://codepen.io/MichaelArledge/pen/pOLapW

Did this work before? No 

Chrome version: 69.0.3497.81  Channel: stable
OS Version: OS X 10.13.5
Flash Version:

Comment 1 by ajha@chromium.org, Sep 13

Cc: ajha@chromium.org
Components: -Blink Blink>Layout
Labels: Target-71 FoundIn-71 M-71 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on the latest canary 71.0.3551.0 and on the latest stable 69.0.3497.92 on Windows-10, Mac OS 10.13.6 and Linux Debian Rodete. Seeing similar behavior on older chrome version 60.0.3112.20 as well.

Marking this as Untriaged for more inputs from the respective team.
883355.jfif
546 KB Download

Comment 2 by ajha@chromium.org, Sep 13

883355.jpg
365 KB View Download

Comment 3 by e...@chromium.org, Sep 13

Owner: szager@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by szager@chromium.org, Sep 14

Status: WontFix (was: Assigned)
That is the expected behavior; opacity does not affect IntersectionObserver.
►

Sign in to add a comment