WICG / WICG/PEPC

Enum values that ignore naming conventions in The HTML Permission Elements

Open
#87 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
72
Forks
15
PR merge metrics
No merged PRs in 30d

Description

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

  • The value "illegal_subframe" of the enum InPagePermissionMixinBlockerReason does not match the expected conventions (lower case, hyphen separated words)
  • The value "unsuccesful_registration" of the enum InPagePermissionMixinBlockerReason does not match the expected conventions (lower case, hyphen separated words)
  • The value "recently_attached" of the enum InPagePermissionMixinBlockerReason does not match the expected conventions (lower case, hyphen separated words)
  • The value "intersection_changed" of the enum InPagePermissionMixinBlockerReason does not match the expected conventions (lower case, hyphen separated words)
  • The value "intersection_out_of_viewport_or_clipped" of the enum InPagePermissionMixinBlockerReason does not match the expected conventions (lower case, hyphen separated words)
  • The value "intersection_occluded_or_distorted" of the enum InPagePermissionMixinBlockerReason does not match the expected conventions (lower case, hyphen separated words)
  • The value "style_invalid" of the enum InPagePermissionMixinBlockerReason does not match the expected conventions (lower case, hyphen separated words)
  • The value "type_invalid" of the enum InPagePermissionMixinBlockerReason 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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the linked The HTML Permission Elements specification and locate the InPagePermissionMixinBlockerReason enum. Review the eight listed values against the cited casing guidance, then verify the specification consistently uses lower-case, hyphen-separated values and that all enum references remain coherent.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.