Skip to content

fix: handle unparseable @container conditions with error_recovery #1330

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.

Sign up for GitHub

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

Open
Larslllllll wants to merge 1 commit into
base: master
Choose a base branch
from
+6 −0
Open

fix: handle unparseable @container conditions with error_recovery #1330

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/parser.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -674,6 +674,12 @@ impl<'a, 'b, 'i, T: crate::traits::AtRuleParser<'i>> AtRuleParser<'i> for Nested
if name.is_some() && input.is_exhausted() {
// name only, no condition - allowed by new syntax
AtRulePrelude::Container(name, None)
} else if self.options.error_recovery {
// When error recovery is enabled, use Unknown for unparseable conditions
// instead of propagating the error. This allows the CSS to be parsed
// despite unsupported @container syntax (e.g., future scroll-state queries).
self.options.warn(e);
AtRulePrelude::Container(name, Some(ContainerCondition::Unknown(TokenList::parse(input, &self.options, 0)?)))
} else {
// condition parsing failed (e.g., empty brackets or invalid tokens)
return Err(e);
Expand Down