When running with OOP-D you can't click on OOPIFs. This is due to early outs before any of the SurfaceHittest code. Running the following command line and looking at a page with ads demonstrates this.
$ ./chrome --enable-features=VizDisplayCompositor,top-document-isolation
It looks like OOP-D and site-per-process is pretty unstable but top-document-isolation works for testing this out. If we could get the slow path hit testing working, where the browser always asks the renderer, that would at least make OOPIFs usable.
Comment 1 by kylec...@chromium.org
, Jan 22 2018Summary: viz: Make OOPIF hit testing work with OOP-D (was: viz: Make OOPIF hit testing working with OOP-D)