New issue
Advanced search Search tips

Issue 726763 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

WebFrameWidgetImpl should not use FocusedOrMainFrame

Project Member Reported by dcheng@chromium.org, May 26 2017

Issue description

Most things here are also implemented on WebViewImpl. (I'm told) there are IPC races that can make it so we no longer have a focused frame by the time the message gets to the renderer: in this case, we should not fall back to the main frame. After all, the WebView doesn't have anything to fallback to when it loses the IPC race.
 
Is it reasonable to say that, ideally, no IPCs requiring WebFrameWidget are allowed to arrive at the renderer with no WebFrameWidget?

Maybe we should block sending any IPCs (in need of WebFrameWidget) as soon as the main frame swaps out (and is deleted) until the RenderView swaps back in?
I guess in all similar use cases for WebViewImpl (which is probably duplicate code to be separated) we should not be using FocusedOrMainFrame either. The ones I can think of are IME and editing methods.
Project Member

Comment 3 by sheriffbot@chromium.org, May 31 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.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
(We still want to work on this, but it's not very high priority)

Sign in to add a comment