Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Focus area descriptions #919

Merged

Conversation

captainbrosset
Copy link
Contributor

No description provided.

@DanielRyanSmith
Copy link
Contributor

This will need to be merged if we want it available on the dashboard for the release date. Has there been any movement on this?

@captainbrosset
Copy link
Contributor Author

The plan is, I think, to merge it on launch day, moments before the dashboard goes out.
I've not received any feedback so far on the PR. Note that there had been some healthy amount of feedback on the document which this PR comes from. So this has already gone through one round of review.

@zcorpan
Copy link
Member

zcorpan commented Feb 12, 2025

Suggestions by @nt1m (from email) which I agree with:

Navigation -> Navigation API (“Navigation” is a pretty vague term by itself)
WebAssembly -> WebAssembly Additions (the current focus area does not cover all of WebAssembly)
Privacy -> Privacy Testing (We may want to do the same for Gaming / WebVTT depending on what the investigation is supposed to cover)

@jgraham
Copy link
Contributor

jgraham commented Feb 12, 2025

WebAssembly -> WebAssembly Additions

Without wanting to bikeshed, we have fairly often chosen more generic names over less generic ones (c.f. "WebRTC" which isn't the entire WebRTC API, "Layout" which isn't all of CSS, etc.). I think "additions" in particular doesn't add much value in the name since many focus areas are about adding new functionality to an existing broad area of the platform and ends up sounding a bit like the feature is to do with arithmetic.

@nt1m
Copy link
Member

nt1m commented Feb 12, 2025

WebAssembly -> WebAssembly Additions

Without wanting to bikeshed, we have fairly often chosen more generic names over less generic ones (c.f. "WebRTC" which isn't the entire WebRTC API, "Layout" which isn't all of CSS, etc.). I think "additions" in particular doesn't add much value in the name since many focus areas are about adding new functionality to an existing broad area of the platform and ends up sounding a bit like the feature is to do with arithmetic.

I think there's a balance to reach, we don't use "Color" for "Relative Color Syntax" for instance. Perhaps something like WebAssembly JS integration or whatever name is appropriate.

I'd probably suggest a longer name for WebRTC too, but I don't think there's a more detailed name that makes sense that isn't too long for the dashboard. Ditto for Layout.

@foolip foolip merged commit 1c88a58 into web-platform-tests:main Feb 13, 2025
@captainbrosset captainbrosset deleted the focus-area-descriptions branch February 13, 2025 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants