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

Interfaces sometimes incorrectly marked as supported #251

Open
SebastianZ opened this issue Jul 20, 2024 · 0 comments
Open

Interfaces sometimes incorrectly marked as supported #251

SebastianZ opened this issue Jul 20, 2024 · 0 comments
Labels

Comments

@SebastianZ
Copy link
Collaborator

Chrome 128 implements the SnapEvent interface, though does not support its constructor. Therefore, creating a SnapEvent object fails.

Though as the interface is supported, the tests succeed, even for properties that don't exist.

E.g. using the following test

SnapEvent: {
	links: {
		dev: '#snap-events',
		mdnGroup: 'DOM',
	},
	tests: ['foo'],
	interface: function() {
		return new SnapEvent('scrollsnapchange');
	},
},

the property foo is claimed to be supported.

So, when creation of the interface fails, the tests for the properties should also fail.

Sebastian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant