While this is still triggered by the subresource_filter component (and Safe Browsing checks), it would be best to keep this in blocked_content near other popup blocking code, to avoid coupling and bugs.
cc avi as FYI, since we are planning on moving most of this logic into ui/blocked_content, to live alongside the traditional popup blocker.
I'll try to land this after M63 has its branch cut, so we have low risk of breaking anything with this refactor.
Comment 1 by bugdroid1@chromium.org
, Sep 8 2017