flutter_html_css_stylesheet 0.2.1

A flutter_html extension that resolves a CSS stylesheet and writes each element's winning declarations into its inline style, so extensions can read them.

0.2.1

• Depends on flutter_html_css_core for inline declaration splitting. parseDeclarationList now delegates to the core package's splitDeclarations, which splits on ; outside quotes as well as parentheses. The local splitter only tracked parentheses, so url("a;b.png") inside an inline style was mis-split before this change.
• The stylesheet-rule reader's !important stripping now goes through the core package's stripImportant instead of a local lastIndexOf('!') check. No behaviour change for well-formed input; StylesheetDeclaration and every other public symbol are unchanged.

0.2.0

• Renamed from flutter_html_css_stylesheet_extension on pub.dev. The old package stays published and is marked discontinued with this one as its replacement. Class names are unchanged.

0.1.0

• Initial release. flutter_html 3.0.0 does read <style> blocks, then hands every declaration to declarationsToStyle(), which knows 51 property names and drops the rest before any extension runs, so a stylesheet rule could never reach the family. This one resolves the cascade itself and appends each element's winning declarations to its inline style="" at the preStyling step, where the siblings already look. Register it first or they read the attribute before the rules land in it.
• Selectors go through StyledElement.matchesSelector, so you get type, class, id, attribute and :not() selectors plus all four combinators, and not much else. The selector reference has the tables.
• consumeStyleElements defaults to true and empties each <style> element once it has been read. Not tidiness: upstream parseExternalCss() throws a LateInitializationError on @media and a TypeError on @keyframes with nothing of ours registered, and emptying the block is what keeps it away from them.
• onUnsupportedRule names every rule that renders nothing: at-rules, pseudo-elements, and any pseudo-class the matcher cannot evaluate. Leave it off and they go in silence, which is the failure mode this package will get blamed for.