New issue
Advanced search Search tips

Issue 917796 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 28
Cc:
dgozman@chromium.org
hirosh...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Worker top-level scripts appears like worker subresource in DevTools when off-the-main-thread fetch is enabled

Project Member Reported by hirosh...@chromium.org, Dec 26 
ToT (r618847; OffMainThreadWorkerScriptFetch is not yet shipped)

What steps will reproduce the problem?
(1) Run chrome with --enable-blink-features=OffMainThreadWorkerScriptFetch
(2) Open DevTools
(3) Open http://mdn.github.io/simple-web-worker/

What is the expected result?

Current behavior without OffMainThreadWorkerScriptFetch:

omt-disabled.png: worker.js is shown as a resource on the main thread (without ⚙ mark).

What happens instead?

omt-enabled.png: worker.js is shown as a subresource on the worker (with ⚙ mark).

I'm not sure this difference matters or not and thus anyway filing this.
omt-disabled.png
19.0 KB View Download
omt-enabled.png
23.6 KB View Download

Comment 1 by falken@chromium.org, Dec 27 

dgozman: Can you help triage this? It'd be useful to know the significance of the ⚙ mark (and it's hard to search for documentation about it).

Comment 2 by dgozman@chromium.org, Dec 28

Status: WontFix (was: Untriaged)
I think the version where we show gear icon next to the worker script is actually better. The gear indicates resources related to workers, and worker main script is definitely related to the worker. Thank you for double-checking!
►

Sign in to add a comment