这是indexloc提供的服务,不要输入任何密码
Skip to content

API hooks to detect if a third-party iframe/embed is compliant or not, so first-party apps can show provide fallback options #302

@aaudu-codaio

Description

@aaudu-codaio

Per Ben Kelly wanderview@chromium.org on Wed, 27 Mar 2024 at 15:03 filing here.

Expanding on Adam Gertenbach’s excellent feedback, we’re wondering what options we have as a first-party web app, in the likely scenario that a third-party app doesn’t update their iframe/embeds, and we’re past the deprecation trail (DT) period with third-party cookies phased out?

We’re concerned about the customer experience and reputation impact to our first-party app, hosting the third-party iframe. We’re hoping for some programmatic hooks or options we can leverage as a first-party, so we can provide some affordance to educate our customers.

Blink-dev response page types (1)
Blink-dev response page types

For example, you could imagine similar to the Google new sign-in page notice or older Google chrome plug-in crash butter bar — see screenshots below, we show a similar notice for third-party iframes/embeds that are out of compliance or some other experience e.g., break glass, so we have an opportunity to customers and set expectations accordingly.
image.pngimage.png

We wanted to call out this scenario and see if we missed options here we can leverage as this feature rolls out to all chrome users.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions