NOTREACHED() in WebRemoteFrameImpl::removeSpellingMarkers() under --top-document-isolation |
|||||||
Issue descriptionFrom a user report: """Which sites work with TDI. Tried enabling TDI via about:flags on a ChromePublic build today. Tried CNN, theverge, techchrunch, and they all die with a NOT_IMPLEMENTED in WebRemoteFrameImpl::removeSpellingMarkers. Known issue? work-around?""" I can't so far repro this on a Windows debug build with cnn.com, so assuming this is an Android issue. If we're reaching this there may be spellcheck correcntess bugs w/ oopifs in general.
,
May 25 2016
Spellcheck does need work for OOPIF, yes. Happy to assist anybody who can migrate it, but currently don't have spare cycles to do it myself. (Also, pointer to docs appreciated :)
,
May 27 2016
https://codereview.chromium.org/2012823003/ will remove removeSpellingMarkers from WebRemoteFrameImpl - it's only useful on WebLocalFrame. Please recheck once this has landed (or the associated bug #604645 has been closed)
,
Jun 21 2016
Issue 622039 has been merged into this issue.
,
Dec 7 2016
Should this be resolved as duplicate of issue 638351? Or at least being blocked on it?
,
Dec 7 2016
WebRemoteFrameImpl::removeSpellingMarkers has been removed, bug#604645 has long since landed. I'd suppose we can close this?
,
Jan 5 2017
Closing per comment 6.
,
Jan 5 2017
,
Apr 27 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by creis@chromium.org
, May 25 2016