New issue
Advanced search Search tips

Issue 654079 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
szager@chromium.org
est...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocking:
issue 647560



Sign in to add a comment

IntersectionObserver descendant console warning is spammy

Project Member Reported by esprehn@chromium.org, Oct 7 2016 
https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/dom/IntersectionObserver.cpp?q=IntersectionObserver.cpp&sq=package:chromium&l=287

This means if you create an IntersectionObserver for an Element in a document with no frame (ex. document.implementation.createHTMLDocument()) or one inside a <template> you get a warning in the console. It also only catches the first observation, not removing and reparenting later. If we want to warn about IO instances that are setup wrong we should add a DevTools feature for that, but I don't think we should warn by default on observe().

This is making it hard for estartk@ to use ElementVisbilityObserver in the C++ since we end up spamming console warnings if we start observing in InputType before we're inserted into the document in some situations.

Comment 1 by esprehn@chromium.org, Oct 7 2016 

Actually this is more than just frameless documents, it also spams for all observers created for elements before they're inserted. :/

I'm not sure what to tell estark@ here, we can add a special path to disable the warning in C++, but I'd rather just remove the warning.

Comment 2 by est...@chromium.org, Oct 7 2016

Blocking: 647560

Comment 3 by l446240525@gmail.com, Oct 8 2016 

https://bugs.chromium.org/p/chromium/issues/detail?id=617393

Actually when I first tried IntersectionObserver API several months ago, I wrongly thought this API could observe any two elements's intersecting, so maybe other developers will need this warning?

Comment 4 by tkent@chromium.org, Oct 14 2016

Components: -Blink>DOM Blink>Layout

Comment 5 by dgro...@chromium.org, Oct 14 2016

Status: Available (was: Untriaged)

Comment 6 by ojan@chromium.org, Mar 7 2017

Cc: -ojan@chromium.org
Project Member

Comment 7 by sheriffbot@chromium.org, Mar 9 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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

Comment 8 by e...@chromium.org, Mar 16 2018

Status: Available (was: Untriaged)
►

Sign in to add a comment