-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include css files in browser #431
Comments
Yep, let's extend the web server to properly serve css files. (Instead of |
Yes we need to be able to include CSS files as it useful for the tests : transition events, sizing, jQuery selectors... |
Hey @vojtajina, I'm up for making a PR for this. AngularJS needs it for including the |
@matsko absolutely! |
@vojtajina this is what you had in mind when we spoke earlier right? |
Yep On Fri, Jun 14, 2013 at 5:05 PM, Matias Niemelä [email protected]:
|
👍 am running into the same issue here too. Would be happy to collaborate on a PR too. |
thanks @timols ! |
Hi @vojtajina do you have this slated for release 0.9.5? |
is it in latest 0.10 release yet? I do not see anything in docs related to how to use it. Thanx! |
nevermind, looked at sources,
works just fine. |
Is this broken again in karma 0.12.16 ? I tried including a CSS file using this:
Then going to debug.html I inspected the "head" tag of the page but there is no "link" tag appearing. I couldn't find any useful information related to this feature after googling. |
Hmmm... I was looking in the wrong place. They seem to be included in the "body" tag instead. Thanks. |
@PVince81 Edit: Lied I can but I didn't have to include a |
Don't work in my case. Version of Karma: 1.6.0. Additional I'm using Config: https://github.com/bupy7/js-cropbox/blob/master/Gruntfile.js#L41 What do I do wrong? May be |
Some of my tests require css libraries to be included such as Bootstrap. Currently I don't see a way of doing this. It would be nice if Karma would allow for specifying css files in a fashion similar to javascript files.
The text was updated successfully, but these errors were encountered: