Who else is missing dark mode for Service Worker page?

[Juraj M.]

I've made a request here:
https://issues.chromium.org/issues/442444722

I've been working with service workers for a past few weeks and this page is killing me.

Is there maybe some workaround I could use to invert the page?

[kg_17]

In chrome://flags, enable 'Auto Dark Mode for Web Contents'.

[Juraj M.]

Thank you for the tip!

It works great for that specific page, but all other normal pages looks terrible, it activates even on my extension page.

Any chance I can enable only for the specific page? I can't find any control panel.

[kg_17]

It's not quite ideal, but an extension service worker can also be viewed by opening DevTools in an extension page (under Application) or a web service worker by opening DevTools on a web page.  The DevTools will be dark if dark mode is enabled in chrome://settings/appearance. 

[woxxom]

Instead of using that page, open Devtools on any of your extension's pages or on chrome-extension://id/manifest.json -> Application -> Service worker -> use the buttons to start/stop the service worker.

[Juraj M.]

Well, I have a bit of a special case now...

I'm converting my extension into web app, so I need to open Service worker of the web app, not extension.

Specifically, I want to see the Service worker console, so I'm looking for the "Inspect" button, but I don't see it in the "Application" tab.

I can see it only on the chrome://serviceworker-internals/ page.

Look, it even shows me there are two errors in the "background.loader.js", but clicking it only focuses current window console, instead of opening the worker console. Maybe I should actually report this as a bug, right?

[woxxom]

In that case you need two devtools instances: one for the web app and another one for an extension page or its chrome-extension://id/manifest.json if the extension doesn't have any pages.

[woxxom]

Scratch that, I think I know what happens. Chrome combines devtools for the web app and its service worker by design, so you don't need another console, you can see the output right in this devtools. You can also debug the service worker's scripts in this devtools. The console combines the output of the page and the service worker so if you want to see only the SW's output, tick "[x] Selected context only" in the console's config.

[Juraj M.]

Oh, you are correct, the console output is indeed merged.

That explains why is my app logging so much...

I definitely prefer seeing "background script" logs in a separate window.

I think I need to read the MDN again because I'm getting stuck with strange issues whole day. Or is that a normal phenomenon for working with Service workers? :)

[Patrick Kettner]

Dakujem for the suggestion Juraj! I sent in a PR to chromium the day you brought it up, and it was finally merged. It should (hopefully) start showing up in canary Friday, and then ultimately in Chrome 142.

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/cf99b6a6-5dce-468b-bfe2-d5bd93452c36n%40chromium.org.

[Juraj M.]

Oh man, what a great news!
Thanks a lot Patrick :), now I'm regretting I haven't ask for it years ago :D.

And how did you know that I'll know what "Ďakujem" means? :D
Are you secretly a Slovak/Czech? :)

Anyway, thank you for making my programming life easier!