New issue
Advanced search Search tips

Issue 608005 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
dcheng@chromium.org
bokan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Determine use a standard check for when Blink is in "shutting down" phase

Project Member Reported by bokan@chromium.org, Apr 29 2016 
There's some context and discussion here: https://codereview.chromium.org/1930323002/

In short, we sometimes check for a null m_page pointer, sometimes we check for a null m_client. There's cases where the passed in m_client can be null. Maybe it's best to just set a separate bit when WebViewImpl::close() is called and check that? (Assuming WebViewImpl::close is the true shutdown signal).
Project Member

Comment 1 by sheriffbot@chromium.org, May 1 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

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

Comment 2 by bokan@chromium.org, May 9 2017

Labels: Hotlist-Input-Dev
Status: Available (was: Untriaged)
I think this is still an issue that could use some cleanup for input handling.

Comment 3 by dtapu...@chromium.org, Oct 26 2017

Components: Blink>Internals
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 29

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.

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

Sign in to add a comment