-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
docs(elements): move clarification about custom elements #30594
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Can you please change the commit message to something like:
docs(elements): move clarification about custom elements
...
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
Updated the commit message, forgive me if this isn't the format you're looking for. First contribution to open source (even if small) :) |
Proc for cla/google bot |
proc cla/google bot 2: electric boogaloo |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
Moved clarification that "custom elements" are a subtype of Web Components to the first use of the term "custom elements"
Moved clarification that "custom elements" are a subtype of Web Components to the first use of the term "custom elements" PR Close #30594
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Moved clarification that "custom elements" are a subtype of Web Components to the first use of the term "custom elements"
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
No code changes
Does this PR introduce a breaking change?