Permission Revocation - English language clarification
Nadie ha tomado este issue todavía.
- #363 de @karlcow — cerrado sin fusionar
Evaluación
- Dificultad
- 1/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Estancado
- Stack tecnológico
- html
- Área
- documentation
Línea de trabajo
Read the revocation text in the security and privacy considerations and compare it with the pushsubscriptionchange event section referenced in the issue. Clarify the nested wording while preserving the stated event fields and deactivation requirement; done means the revocation text is easier to understand without changing its meaning.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
In the security and privacy considerations, there is this section about revocation. To note that this is the only section of the specification where revocation is explained.
When a permission is revoked, the user agent MAY fire the "pushsubscriptionchange" event for subscriptions created with that permission, with the service worker registration associated with the push subscription as registration, a PushSubscription instance representing the push subscription as oldSubscription, and null as newSubscription. The user agent MUST deactivate the affected subscriptions in parallel.
It has too many with in a row to make it clear (at least for ESL like me).
Would there be a way to rephrase this to make it clear? I put the red dots where it starts to be confusing in the level of English nesting.
When a permission is revoked,
- the user agent MAY fire the "pushsubscriptionchange" event
- for subscriptions created with that permission
- 🔴 with the service worker registration associated with the push subscription as registration,
- 🔴 a PushSubscription instance representing
- the push subscription as
oldSubscription, - and
nullasnewSubscription.
- the push subscription as
- The user agent MUST deactivate the affected subscriptions in parallel.
Other mentions of revocation.
Then in 10.5 The pushsubscriptionchange Event
The pushsubscriptionchange event indicates a change in a push subscription that was triggered outside of the application's control, for example because it has been refreshed, revoked or lost.
And in the security and privacy section with
Permissions that are preserved beyond the current browsing session MUST be revocable.
- Lenguaje dominante
- HTML
- Estrellas
- 158
- Forks
- 43
- Merge medio
- 2 d 6 h
- PR fusionados (30 d)
- 2
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de w3c/push-api
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
-
Do we want to allow a subscription from window.pushManager to fire push event for non-DWP messages?Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 18/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 12/100
Todos los issues de w3c/push-api
Issues similares
-
Page request: clang-replAbiertohelp wanted new command
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
tldr-pages/tldr#25111 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
code-yeongyu/senpi#6375 ·
Los mantenedores suelen responder en 1 día
-
documentation
Dificultad 1/5 1-3 horas Aptitud para principiantes 83/100
MysterionRise/pubchem-finder#108 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
ktwu01/benchmark-radar#1220 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 98/100