Thanks Jungkee. I'm not sure about reverting the spec. If the plan is to make it empty string in the end, it'd be better to start making that change in the implementations sooner than later. If it's better for devs to be the empty string, I think I'm comfortable making the change (I'm trying to investigate whether sites that would break). But I don't quite get how the semantics changed: even with resultingClientId, clientId for navigations is non-existent/null/empty and it seems that could be validly expressed as empty string or null. It'd be good to know what WebKit does. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1266#issuecomment-361843574
Received on Wednesday, 31 January 2018 07:09:27 UTC