MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers

[PerformanceControlOfEmbeddedContent] Further details for the embedee experience

Open
#978 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Performance Control of Embedded Content
Dominant language
HTML
Stars
1.4k
Forks
286
Avg merge
3d 1h
Merged PRs (30d)
8

Description

Hi,

I run a web platform where the majority of our content is embedded into our clients.

I would love to understand more about the experience for us (the embedee).

Would we be able to be notified when the site embedding our content has taken an action? What would the mechanism for this look like?

What information might we get about where the violation had occurred? For instance, a client might have our content on multiple pages and I could imagine cases where the content triggers a violation on certain pages but not others. (Is that assumption correct?) Would we be able to see the page and anything else about the context the page the content is embedded in?

I'll have a think about other cases - but we'd certainly be interested in understanding how we make sure we're doing well.

Thanks
Ed

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the PerformanceControlOfEmbeddedContent explainer and review the existing issue discussion about the embedee experience. Done would mean documenting whether embeddees can receive action notifications and what violation, page, and embedding context information is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.