css86 B

Minified CSS with an external source map

A minified stylesheet closing with the CSS form of the annotation, `/*# sourceMappingURL= */` - the comment syntax differs from JavaScript's and is a common reason a CSS map is silently ignored. For testing stylesheet source-map resolution.

Web assets Code parsing Syntax highlighting

Preview — first 3 linescss

.card{color:#059669;border-radius:12px}
/*# sourceMappingURL=sourcemap-css-v3.json */

Specifications

Seed: 70400
Site: example.com (fictional)
Generated Lines: 1
Source Mapping URL: sourcemap-css-v3.json
Annotation Syntax: /*# ... */

Testing contract

Expected to pass

Scenario: Open the stylesheet in a tool that resolves CSS source maps.
Expected result: The /*# ... */ annotation is recognised (not skipped as an ordinary comment) and the declaration at column 6 maps to src/base.css line 2 column 3.

What is a .css file?

CSS (.css) is a plain-text stylesheet describing how HTML elements are presented — colors, layout, typography, and responsive behaviour. It uses selectors paired with declaration blocks, and modern CSS adds custom properties (variables), flexbox and grid layout, and media queries.

How to use this file

Use an example .css file to test syntax highlighters, CSS parsers and minifiers, linters (stylelint), and pipelines that process or bundle stylesheets.

How to use this file for testing

“Minified CSS with an external source map” is a deterministic Novus Examples fixture for Web assets, Code parsing, Syntax highlighting. Favicons, web app manifests, service workers, robots and sitemap files, Open Graph images, and .well-known resources — for testing web tooling, crawlers, PWA installers, and asset pipelines.

Documented properties for this file: seed 70400. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Web-platform fixtures are standards-compliant samples against fictional example.com data. Test crawlers, PWA installers and manifest validators, favicon/icon pipelines, service-worker registration, or .well-known parsers against the documented structure.