The only difference between this commit and the previous is that I have used a difference scheme for naming Jasmine CSS classes. Instead of appending "_jasmine-css" to all Jasmine CSS selectors, I have now preprended "jasmine-" instead.
As described in Issue Report 844... #844 ...style rules in the app-being-tested may incidentally affect elements in the Jasmine HTML Report container, as long as there is a chance that the app-being-tested has CSS style rules for classes (or IDs) that Jasmine uses. This fix attempts to bring Jasmine to a state where each and every class it uses always ends with "_jasmine-css" which should be unique enough to ensure that CSS in the app-being-tested won't affect the Jasmine report, because no app-being-tested is ever likely to use classes that end with "_jasmine-css" I'll be surpised if this commit is good enough as it is now, on the first attempt to fix #844, because of reasons I'll explain in either the Issue or the Pull Request.
- When no specs were focused, they all had the same precedence, and `sort`ing them caused some of the nodes to move around Fixes #850
… page Fix #603
I removed the `.showDetails` and `.summaryMenuItem` styles from the Sass file because I believe that no HTML elements with those classes will ever be generated by Jasmine and that they are dead code that someone forgot to remove. This is my first contribution to the Jasmine project and so I might be doing something wrong, but I believe just this one change will propagate to all the generated code when it is built, and that I should not be altering any other code in any other place to accomplish the change I intend. This is related to Jasmine Issue 847: #847