WebIDL namespaces can have members which are divided into "operations", "consts" and "attributes" as defined in the spec.
While all of these members are parsed correctly by weedle, attributes get explicitly ignored by wasm-bindgen-webidl (using a match-all underscore and simply returning Ok):
|
match self { |
|
weedle::namespace::NamespaceMember::Const(const_) => { |
|
record |
|
.namespaces |
|
.get_mut(ctx.0) |
|
.unwrap() |
|
.consts |
|
.push(ConstNamespaceData { |
|
definition: const_, |
|
stability: ctx.1, |
|
}); |
|
Ok(()) |
|
} |
|
weedle::namespace::NamespaceMember::Operation(op) => op.first_pass(record, ctx), |
|
_ => Ok(()), |
|
} |
This currently blocks inclusion of the new APIs like the CSS Custom Highlight API which introduces the highlights attribute into the CSS namespace, as encountered in PR #4792.
WebIDL namespaces can have members which are divided into "operations", "consts" and "attributes" as defined in the spec.
While all of these members are parsed correctly by weedle, attributes get explicitly ignored by
wasm-bindgen-webidl(using a match-all underscore and simply returning Ok):wasm-bindgen/crates/webidl/src/first_pass.rs
Lines 1463 to 1478 in 06c78f0
This currently blocks inclusion of the new APIs like the CSS Custom Highlight API which introduces the
highlightsattribute into theCSSnamespace, as encountered in PR #4792.