As part of quick actions support, content detectors in the renderer are being removed. For one milestone they will be disabled, but not fully removed. After that they can (and should be) removed entirely.
This has gone stable so we can start with the deletion. Copy-pasting what I wrote on a thread about the little that needs to be preserved in WebView:
"I looked into the implementation of the WebView public APIs and I believe we can delete a majority of the content detection code without regressing any public API behavior.
On Tue, Nov 8, 2016 at 4:05 PM, Bo Liu <boliu@google.com> wrote:
> Also usage of these content detectors is a bit wider in chrome than webview:
> * fire intents if user clicks on an address/phone number, same as chrome
> * implement these hittest schemes, which are then used by apps to populate their context menu
As far as I see, this actually does not use the content detector at all today. All it does is a simple scan of a link URL to see if it starts mailto://, geo:// or tel://. See aw_render_frame_ext.cc
> * implement webview.findAddress
This uses the static method findAddress but not anything else. See content_view_statics.cc
So I think we should go forward with deleting everything except for findAddress and the methods it depends on.
Comment 1 by bugdroid1@chromium.org
, Nov 11 2016