Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update report on Enum values that ignore naming conventions in HTML Standard #750

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

dontcallmedom-bot
Copy link
Contributor

This pull request was automatically created by Strudy upon detecting errors in Enum values that ignore naming conventions in HTML Standard.

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/whatwg/html.

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 HTML Standard
Tracked: >-
The CanvasTextRendering names are inherited from SVG and seem widely deployed;
flipY seems widely supported (according to WPT)
Repo: 'https://github.com/whatwg/html'

While crawling HTML Standard, the following enum values were found to ignore naming conventions (lower case, hyphen separated words):

  • The value "optimizeSpeed" of the enum CanvasTextRendering does not match the expected conventions (lower case, hyphen separated words)
  • The value "optimizeLegibility" of the enum CanvasTextRendering does not match the expected conventions (lower case, hyphen separated words)
  • The value "geometricPrecision" of the enum CanvasTextRendering does not match the expected conventions (lower case, hyphen separated words)
  • The value "flipY" of the enum ImageOrientation 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.

@dontcallmedom dontcallmedom merged commit 059f54e into main Sep 9, 2024
1 check passed
@dontcallmedom dontcallmedom deleted the html-wrongcaseenumvalue branch September 9, 2024 10:15
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.

3 participants