test clarification: multiple 'valid' syntax cases use legacy extended attributes

[nektro]

https://github.com/w3c/webidl2.js/blob/91b2878/test/syntax/idl/identifier-hyphen.webidl
https://github.com/w3c/webidl2.js/blob/91b2878/test/syntax/idl/namedconstructor.webidl
https://github.com/w3c/webidl2.js/blob/91b2878/test/syntax/idl/nointerfaceobject.webidl
https://github.com/w3c/webidl2.js/blob/91b2878/test/syntax/idl/overridebuiltins.webidl
https://github.com/w3c/webidl2.js/blob/91b2878/test/syntax/idl/treatasnull.webidl

all of these throw validation errors when passed through the checker.

this is corroborated by https://github.com/w3c/webidl2.js/blob/91b2878/test/invalid/idl/renamed-legacy-extattrs.webidl
and whatwg/webidl#870

^ [TreatNullAs] extended attribute is a legacy feature that is now renamed to [LegacyNullToEmptyString]. Refer to the relevant upstream PR for more information.

is this an issue or a detail i'm missing?

[saschanaz]

That "syntax" tests are literally just syntax tests, having a wrong extended attribute shouldn't make a syntax issue. They still may make some validation issues, but that's fine.

[nektro]

ohhh i see.