Q: Karma launchers HTML5 APIs I can't find any documentation to confirm or deny that the karma launchers support HTML5 in the browsers. Yet my tests are failing because of some missing HTML5 capabilities. This happens for Firefox, Chrome and PhantomJS. However, everything works as expected when I use the actual browser.
I'm using the mule-uploader library which checks for HTML5 APIs before continuing like so:
// verify that the browser has the needed HTML5 capabilities
if (!(namespace.File && namespace.FileList && namespace.Blob && namespace.FileReader && namespace.Worker)) {
    log("HTML5 APIs not available.");
    return -1;
}

Do the karma launchers support HTML5?

A: A karma launcher is just a bunch of scripts (in JS, bash or Windows shell) to launch a program - effectively a browser - with some arguments in order to have a clean instance to use.
The HTML5 capability is something related to the browser itself and not to the script that is invoking it - as far as I know you cannot invoke a browser with a --no-html5 flag.
Have a look at the source code of a karma launcher: Chrome launcher, Firefox Launcher, etc...
So between a karma launcher and the HTML5 there's no correlation as far as I know.
What it can happen is that the launcher is invoking an old version of the browser without the particular HTML5 capability you're looking for.
Try to set some logs in one of the launchers (there are usually no loggers in these plugins) and see the path they're pointing at: there should be a DEFAULT_CMD object with the paths for each OS defined in the file.
