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.

Sign up for GitHub

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

Jump to bottom

Inconsistent usage of "[[control thread state]]" #2549

Open
gsinafirooz opened this issue Jun 14, 2023 · 2 comments
Open

Inconsistent usage of "[[control thread state]]" #2549

gsinafirooz opened this issue Jun 14, 2023 · 2 comments
Labels
category: editorial Editorial changes that do not affect interpretation. https://www.w3.org/policies/process/#class-2 Needs Edits Decision has been made, the issue can be fixed. https://speced.github.io/spec-maintenance/about/ size: S Small amount of work expected to resolve.

Comments

@gsinafirooz
Copy link

The term "[[control thread state]]" being followed by the word "flag" is inconsistent.
@hoch
Copy link
Member

hoch commented Jul 12, 2023

Can you point the spec location for this?

@hoch hoch added the category: editorial Editorial changes that do not affect interpretation. https://www.w3.org/policies/process/#class-2 label Jul 12, 2023
@mjwilson-google
Copy link
Contributor

I think this is about how sometimes in the spec we say "the [[control thread state]] flag" and sometimes we just say "the [[control thread state]]" -- for instance in https://www.w3.org/TR/webaudio/#dom-offlineaudiocontext-resume step 3 vs step 4. Probably we can just drop the word "flag" since it doesn't seem necessary.

@mjwilson-google mjwilson-google added Needs Edits Decision has been made, the issue can be fixed. https://speced.github.io/spec-maintenance/about/ size: S Small amount of work expected to resolve. labels Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category: editorial Editorial changes that do not affect interpretation. https://www.w3.org/policies/process/#class-2 Needs Edits Decision has been made, the issue can be fixed. https://speced.github.io/spec-maintenance/about/ size: S Small amount of work expected to resolve.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hoch @mjwilson-google @gsinafirooz