-
Notifications
You must be signed in to change notification settings - Fork 170
Replace many uses of the word "interface" #3256
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
base: main
Are you sure you want to change the base?
Conversation
In most places API is more natural and consistent with the rest of web-features. Sanitizer is aligned with the wording in parse-html-unsafe.yml. For WebDriver "interface" isn't wrong, but protocol seems clearer.
@@ -1,5 +1,5 @@ | |||
name: DOM Geometry | |||
description: The `DOMMatrix`, `DOMPoint`, `DOMQuad` and `DOMRect` interfaces offer a way to represent points, rectangles, quadrilaterals and transformation matrices within JavaScript. They can be used in transformations in CSS, `<canvas>`, and SVG. | |||
description: The `DOMMatrix`, `DOMPoint`, `DOMQuad` and `DOMRect` APIs offer a way to represent points, rectangles, quadrilaterals and transformation matrices within JavaScript. They can be used in transformations in CSS, `<canvas>`, and SVG. |
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.
description: The `DOMMatrix`, `DOMPoint`, `DOMQuad` and `DOMRect` APIs offer a way to represent points, rectangles, quadrilaterals and transformation matrices within JavaScript. They can be used in transformations in CSS, `<canvas>`, and SVG. | |
description: The `DOMMatrix`, `DOMPoint`, `DOMQuad` and `DOMRect` APIs represent points, rectangles, quadrilaterals and transformation matrices within JavaScript. They can be used in transformations in CSS, `<canvas>`, and SVG. |
@@ -1,5 +1,5 @@ | |||
name: Sanitizer API | |||
description: The `parseHTML()` method for the `Document` interface and the `setHTML()` methods for the `Element` and `ShadowRoot` interfaces parse and insert HTML into the DOM in a way that can prevent cross-site scripting attacks. The `Sanitizer` API can customize the sanitization process. | |||
description: The `Document.parseHTML()` static method and the `setHTML()` method of `Element` and `ShadowRoot` parses and insert HTML into the DOM in a way that can prevent cross-site scripting attacks. The `Sanitizer` API can customize the sanitization process. |
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.
Something about this read a little off to me. In contrast to Document
, a developer is unlikely to actually touch the Element
and ShadowRoot
interfaces directly, but manipulate instances. What do you think of this change?
description: The `Document.parseHTML()` static method and the `setHTML()` method of `Element` and `ShadowRoot` parses and insert HTML into the DOM in a way that can prevent cross-site scripting attacks. The `Sanitizer` API can customize the sanitization process. | |
description: The `Document.parseHTML()` static method and the `setHTML()` method of `Element` and `ShadowRoot` objects parse and insert HTML into the DOM in a way that can prevent cross-site scripting attacks. The `Sanitizer` API can customize the sanitization process. |
Approved, but with a couple of suggestions. Merge at your discretion. |
In most places API is more natural and consistent with the rest of
web-features.
Sanitizer is aligned with the wording in parse-html-unsafe.yml.
For WebDriver "interface" isn't wrong, but protocol seems clearer.