Open Errata on the Pointer Events Level 3 Recommendation
- Latest Published Version:
- https://www.w3.org/TR/pointerevents3/
- Latest Publication Date:
- June 30, 2026
Open Errata for the Pointer Events Working Group
- Latest errata update:
- Number of recorded errata:
- Link to all errata:
How to Submit an Erratum?
Errata are introduced and stored in the issue list of the group‘s GitHub repository. The workflow to add a new erratum is as follows:
- An issue is raised for a possible erratum. The label of the issue SHOULD be set to “
ErratumRaised”. It SHOULD also include the label corresponding to the document on which the erratum is raised, e.g., “ErratumRaised” . (Please, consult the list of available labels.) It is okay for an erratum to have several labels. In some, exceptional, cases, i.e., when the erratum is very general, it is also acceptable not to have a reference to a document. - Issues labeled as “
Editorial” are displayed separately, to make it easier to differentiate editorial errata from substantive ones. - The community discusses the issue. If it is accepted as a genuine erratum, the label “
Errata” is added to the entry and the “ErratumRaised” label removed. A new comment on the issue MAY also be added, beginning with the word "Summary:" (if such a summary is useful, based on the discussion). - All issues labeled as “
Errata” are displayed in this report, whether they are open or closed. Their status is added to the report on the individual errata. - If the community rejects the issue as an erratum, the issue should be closed.
- Each erratum may be labelled as “
Editorial”; editorial errata are listed separately from the substantive ones. - ALL substantive errata are expected to have corresponding test(s), in the form of either new tests or modifications to existing tests, or must include a rationale explaining why test updates are not required for the erratum.
This report contains a reference to all open issues with the label Errata, displayed in the sections below. Each section collects the issues for a specific document, with a separate section for the issues not assigned to any.
If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Working Group.