We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using platform object example
consider allowing non-matching enums to be converted to a particular value
Support subclassing Array
allow attributes to have different types for their getter and setter
Function's length property is inconsistent with EcmaScript
"a value (matching DefaultValue)"
freeze/seal/preventExtensions should throw for Nodes (and maybe any WebIDL interface)
"optional any" is nonsense that should be disallowed
"The return type of the operation is given by th..."
enum should be able to inherit from another enum
Why do we disallow overloading across partial interfaces?
Stop using "octet" now Consider renaming numeric types to match ECMAScript typed arrays #843
Fixed length sequences of varying types
" The result of converting an IDL value of any b..."
"Prose accompanying an interface with a pair ite..."
factor out "location of properties that usually go on an interface prototype object" wording
Require that promise rejection are instances of error
Remove requirement for prose around iterable<> if object has indexed properties
Allow partial enums -- Allow partial enums #184
Define context variables, such as "context object"
Data properties
Define [LegacyNewObject]
Support holes or undefined values in the sequences as return values?
Inherited method name conflicts with consequential maplike/setlike interfaces should fail
Should probably perform security checks on arguments too, not just this values
Make BufferSource more convenient to use
[EnforceRange] accepts an odd set of input values
iterable declaration and forEach ECMAScript binding issues
FrozenArray only provides shallow immutability
Provide text guidance for rejecting promises
The text was updated successfully, but these errors were encountered:
I'd love it if someone converted this to separate github issues...
Sorry, something went wrong.
No branches or pull requests
Using platform object example
consider allowing non-matching enums to be converted to a particular value
Support subclassing Array
allow attributes to have different types for their getter and setter
Function's length property is inconsistent with EcmaScript
"a value (matching DefaultValue)"
freeze/seal/preventExtensions should throw for Nodes (and maybe any WebIDL interface)
"optional any" is nonsense that should be disallowed
"The return type of the operation is given by th..."
enum should be able to inherit from another enum
Why do we disallow overloading across partial interfaces?
Stop using "octet" now Consider renaming numeric types to match ECMAScript typed arrays #843
Fixed length sequences of varying types
" The result of converting an IDL value of any b..."
"Prose accompanying an interface with a pair ite..."
factor out "location of properties that usually go on an interface prototype object" wording
Require that promise rejection are instances of error
Remove requirement for prose around iterable<> if object has indexed properties
Allow partial enums -- Allow partial enums #184
Define context variables, such as "context object"
Data properties
Define [LegacyNewObject]
Support holes or undefined values in the sequences as return values?
Inherited method name conflicts with consequential maplike/setlike interfaces should fail
Should probably perform security checks on arguments too, not just this values
Make BufferSource more convenient to use
[EnforceRange] accepts an odd set of input values
iterable declaration and forEach ECMAScript binding issues
FrozenArray only provides shallow immutability
Provide text guidance for rejecting promises
The text was updated successfully, but these errors were encountered: