I know you mentioned this and it's on the way. Just creating this issue so that I'll get an email update when done.

Thx a lot!

Not an issue as such but you should be aware that some anti virus programs that actively scan users website behaviour treat (and thus block the page) certain hidden html comments as a threat.

We came across this behaviour last year when commenting out a link to a facebook group page in some html and Kaspersky Antivirus picked it up as a false positive and blocked the entire page from rendering, displaying to the user that the site was compromised. Once the comment was removed the site was fine.

I have contacted Kaspersky regarding this and they say it's expected and intended behaviour.

The moral of the story is be careful what you're commenting out as it may be seen and blocked by third party software and if you don't run the software (like me) then you may never find out and may lose traffic/users etc until someone nice points it out :)

IE8 is not supported because it lacks getComputedStyle

When I read the title and documentation I was really confused. I was thinking about JavaScript debugging breakpoint. I tried to figure out what a HTML breakpoint means (maybe when some properties change in a DOM node) and I couldn't find a reasonable explanation for CSS.

I took me half of the documentation to realize that you were talking about different sizes of browsers.

I would recommend to clearly define breakpoint very early in your docs :)

I'm using Unison with Require.js

require.config({
    paths: {
    unison: '../bower_components/unison/js/unison'
  },
    shim: {
        'unison': { exports: 'Unison' }
    }
});

But then, Unison is loaded after DOMContentLoaded event, and because Unison is registering listener to that event to initialize itself, it will not start correctly.

doc.addEventListener('DOMContentLoaded', function(){
      unisonReady = win.getComputedStyle(head, null).getPropertyValue('clear') !== 'none';
      breakpoints.update();
    });

I managed to fix it, but I'm not sure if it's good approach

if (document.readyState == "complete" || document.readyState == "loaded") {
     // init()
} else {
  doc.addEventListener('DOMContentLoaded', function(){
    // init();
  });
}

I think it'd be very useful if unison.js provided a way for listening when the breakpoint changes.

Something like:

Unison.getBreakpoints().onChange(function(newBreakpoint){
});

Nothing big, but could clear up some confusion folks might have.

In the "How does it work" section you create the breakpoint variables, add them into the $mq-sync list, add the script, and call it done. In reality, that's not all it takes to get this working though because you mention in the next section "Behind the scenes" that there's a breakpoint file where the media queries are generated and some information is saved into the head.

Without reading that part, which comes after things are said to be working, or looking into the repo and looking through breakpoints files it's pretty easy to get lost along the way.

I'd make a pull request of it if the HTML was available in the repo, but it's a pretty small fix anyway. Great job though, looks like a tool with some really interesting possibilities!

Would be cool if this can be installed via bower! Thx

As you can see from my lack of updates, I haven't had time to properly maintain Unison.js. If any of you would be willing to take over and contribute, please let me know. Thanks!

Is there a way to detect when Union is ready?

Why add body:after {content: "xxx"} style if we already get font-family data from head tag?

Trying to get Unison up and running.

Less watcher is throwing the following error:

SytaxError: JavaScript evaluation error: 'ReferenceError: extract is not defined' in ....

Any ideas? Where can I find the extract function/mixin?