Current implementations haven't found a need to show a permission prompt for screen wake lock (or give a way for a user to "deny" the permission).

In particular, I wonder if we should remove:

The [PERMISSIONS] API provides a uniform way for websites to request permissions from users and query which permissions they have.

That's just a "statement of fact".

My suggestion is that we keep the "screen-wake-lock" permission (which is used with Permission Policy - i.e., the HTTP header and allow=), but we then drop "screen-wake-lock" from the Permission spec itself.

We can always add it back later?

@reillyeon @kenchris @rakuco @anssiko - interested in your thoughts on this.