Skip to content

Conversation

@francovs
Copy link
Contributor

@francovs francovs commented Oct 31, 2025

This change is being made in order to exclude PerformanceEventTiming.targetSelector from interop-2025. This specific attribute is currently only in the spec's draft, but it gets picked up automatically by idl tests.

Test variants were added to:

  • event-timing/idlharness.any.js
  • event-timing/idlharness.window.js

In order for this change to work, a new way to exclude tests was added: ?includeIDLMember= and ?excludeIDLMember= will single out specific attributes or operations of interfaces. These should be matched with InterfaceName.attributeName.

@francovs
Copy link
Contributor Author

Unsure if the change to resources/idlharness.js will cause problems with existing code. If there's risk, an alternative is sending a second argument to shouldRunSubTest(), and using that with a different query string such as ?excludeIDL=.

@francovs francovs force-pushed the add-variant-exclude-event-timing-targetSelector branch from 4219c86 to 2b227e2 Compare October 31, 2025 23:53
@wpt-pr-bot wpt-pr-bot requested a review from deniak October 31, 2025 23:53
Test variants which exclude a specific attribute were added to:
- event-timing/idlharness.any.js
- event-timing/idlharness.window.js

In order for this change to work, a new way to exclude tests was added:
`?includeMember=` and `?excludeMember=` will single out specific
attributes or operations of interfaces.
@francovs francovs force-pushed the add-variant-exclude-event-timing-targetSelector branch from 23986da to d1a0aa7 Compare November 4, 2025 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants