This pull request was automatically created by Strudy upon detecting errors in Enum values that ignore naming conventions in Navigation Timing Level 2.
Similar errors had already been detected. Please check that the diff is correct, and that the errors have not already been reported in https://github.com/w3c/navigation-timing.
If everything is OK, you can merge this pull request which will report the issue below to the repo, and update the underlying report file with a link to the said issue.
This pull request was automatically created by Strudy upon detecting errors in Enum values that ignore naming conventions in Navigation Timing Level 2.
Similar errors had already been detected. Please check that the diff is correct, and that the errors have not already been reported in https://github.com/w3c/navigation-timing.
If everything is OK, you can merge this pull request which will report the issue below to the repo, and update the underlying report file with a link to the said issue.
Title: Enum values that ignore naming conventions in Navigation Timing Level 2 Tracked: >- back_forward kept for backwards compat, see https://github.com/w3c/navigation-timing/issues/204#issuecomment-2341052363 Repo: 'https://github.com/w3c/navigation-timing'
While crawling Navigation Timing Level 2, the following enum values were found to ignore naming conventions (lower case, hyphen separated words):
"back_forward"
of the enumNavigationTimingType
does not match the expected conventions (lower case, hyphen separated words)See Use casing rules consistent with existing APIs in Web Platform Design Principles document for guidance.
This issue was detected and reported semi-automatically by Strudy based on data collected in webref.