Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


A ‘Stylefill’ is a way to create new CSS properties using JavaScript. Stylefills are similar in concept to a polyfill, but are only focussed on extending CSS in new ways, and Stylefill.js is a library to help make it much easier.

Disclaimer: This is for people who really know JavaScript. This script will not make anything magically work.

This script acts as a bridge between your CSS and your JavaScript, allowing your scripts to read your invented CSS properties and then run whatever function using the assigned selector and property value.

Use cases

  • Create new properties for CSS and use them in your CSS files.
  • Create polyfills for older browsers that do not require much JavaScript knowledge.
  • Detect CSS property support.


Add stylefill.js to your HTML page, wherever you like. Then, you merely need to initialize stylefill, passing it the new property name and the function you want to run on that property. It’s best to add this at the end of your page, just before the closing body tag.

	<script type="text/javascript">
			'new-property-name' : function-name

In your own javascript, you then create a function that will handle this property. Stylefill.js will parse your CSS and return an array of rule object consisting of three variables to your function:

  • Selector - The selector used for the CSS rule.
  • Property - The invented property name you set.
  • Value - The value given for your property.

This allows you, or anyone working on this CSS, to now write your new CSS properties as if they were real.

header h1 {
	new-property-name: value; /* A brand new property! */
	font-size: 3em;

From there, the sky is your pie. Use the selector to match elements with whatever method you like – use jQuery if you must. Then run through your matched elements and alter them how you like, based on the values you define for your new rules.


View the demo here

In demo.html you will see an example of how this works. For my example, I have created new property to handle ragged edges in typography. I have named the property rag-adjust, and initialize it with Stylefill at the bottom of the HTML.

<script src="./js/stylefill.js" type="text/javascript"></script>
	<script src="./js/typography.js" type="text/javascript"></script>
	<script type="text/javascript">
			'rag-adjust' : typo.ragadjust

I have placed my function in the file typography.js, in which I can build my library of new CSS + JS functions. In the typo.ragadjust function, I use the first few lines to loop through the rules from my CSS find the elements that match the selector I defined there:

for (i in rules) {

	var rule = rules[i],
			eles = document.querySelectorAll(rule.selector),

Here, rule.selector comes straight from my CSS, as I wrote it there. Later, I use the values from my CSS (rule.value) to decide how to manipulate the elements:

if (rule.value == 'small-words' || rule.value == 'all') 
	// replace small words
	elehtml = elehtml.replace(smallwords, function(contents, p1, p2) {
      return p1 + p2.replace(/\s/g, '&nbsp;');

Now, in my CSS, I can write:

p, li, h3, dd {
	max-width: 32em;
	rag-adjust: all; /* My new property */

…and it will be handled just as if it was a real CSS property.

Future proofing

Stylefill.js will check to see if a new property is valid before running your script. If something you’ve built eventually finds its way into the spec, the script will only work as a backup polyfill.


Version 1.2

  • Works with rules in style tags and in linked stylesheets from the same domain. This will fail with rules from a stylesheet on another domain (no cross-domain, basically). Will not read inline styles either.


Create your own CSS properties with JavaScript






No releases published


No packages published