Skip to content

Expose everywhere - #302

Closed
Ms2ger wants to merge 1 commit into
w3c:gh-pagesfrom
Igalia:expose-everywhere
Closed

Ms2ger wants to merge 1 commit into
w3c:gh-pagesfrom
Igalia:expose-everywhere

Conversation

@Ms2ger

@Ms2ger Ms2ger commented Oct 20, 2021 •

Copy link
Copy Markdown

@Ms2ger Ms2ger closed this Jan 18, 2022
@Ms2ger Ms2ger reopened this Jan 18, 2022
@Ms2ger
Ms2ger requested a review from yoavweiss January 28, 2022 08:41
@yoavweiss

Copy link
Copy Markdown
Contributor

Hey! After talking to @domenic, I suspect that actually exposing Resource Timing to ShadowRealms would require a bit more than just an IDL change.

Please correct me if I'm wrong, but IIUC, it could be useful for folks to be able to use Shadow Realms in order to isolate their work from the rest of the document (or other realms). Hence, it could be useful to be able to know which resources your specific ShadowRealm loaded. That would require creating a separate performance timeline per ShadowRealm, and expose those entries there and only there.

Is Fetch aware of ShadowRealms? Would it be possible to pipe the ShadowRealm information from there? Have you looked into what work we'd need to do for PerformanceTimeline?

@yoavweiss

Copy link
Copy Markdown
Contributor

FWIW, once we figure things out for Resource Timing, Server Timing is likely to follow.

@littledan

Copy link
Copy Markdown

fetch and other kinds of I/O (e.g., loading CSS and images) aren't exposed to ShadowRealms. So I'm not sure if resource timing will be very useful. And I can see the argument that, if ShadowRealms do expose resource timing some day, then they should be separated somehow. All together, I'd suggest that we don't merge this PR or the Server Timing one, unless there's something I'm misunderstanding here.

@yoavweiss

Copy link
Copy Markdown
Contributor

Thanks @littledan! That makes perfect sense.

@yoavweiss

Copy link
Copy Markdown
Contributor

Closing for now, but feel free to reopen if you think it's the wrong call.

@yoavweiss yoavweiss closed this Jun 8, 2022
@Ms2ger

Ms2ger commented Jun 9, 2022

Copy link
Copy Markdown
Author

Thanks for looking into this, Dan!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants