Skip to content

Update report on Enum values that ignore naming conventions in Navigation Timing Level 2#1302

Open
dontcallmedom-bot wants to merge 1 commit into
mainfrom
navigation-timing-2-wrongcaseenumvalue
Open

Update report on Enum values that ignore naming conventions in Navigation Timing Level 2#1302
dontcallmedom-bot wants to merge 1 commit into
mainfrom
navigation-timing-2-wrongcaseenumvalue

Conversation

@dontcallmedom-bot

Copy link
Copy Markdown
Contributor

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
w3c/navigation-timing#204 (comment)
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):

  • The value "back_forward" of the enum NavigationTimingType 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.

Cc @dontcallmedom @tidoust

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant