Prior to bug 261038 being resolved, we're still running tests on localhost on the Apple ports. However, localhost is a special case hostname and we should be running them from an insecure context. This causes some bogus failures (and differences between Apple and other ports). We should try just calling internals.markContextAsInsecure() in this case in testharnessreport.js which should improve the situation for testharness.js tests at least (and reftests are probably less likely to be impacted by secure contexts).