"Queue a task" / "in parallel" usage appears wrong · Issue #114 · w3c/geolocation (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

https://w3c.github.io/geolocation-api/#request-position contains this sentence:

Queue a global task using the geolocation task source with global to run the following steps in parallel:

This doesn't really make any sense. Queuing a task is what you do while in parallel, to get back to the main event loop. But you are already on the main event loop. And you can't queue a task to run something in parallel.

https://html.spec.whatwg.org/#event-loop-for-spec-authors may be helpful here. In general it seems like you need an audit of all the steps in the algorithm to ensure that any that involve waiting or talking to external processes (like a location service or permissions checks) happen in parallel, while any that deal with main-thread objects (like callbacks or the current settings object or any data structures like [[watchTasks]]) happen in an appropriately-queued task.