-
Notifications
You must be signed in to change notification settings - Fork 16
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 at bottom #32
Comments
Yes, I'd like to support that. We had this in Fanstatic. In Fanstatic I had a whole complicated infrastructure about declaring resources "bottom safe" and including them by default in the bottom of the HTML file if so. I think we need something simpler in BowerStatic; perhaps just an argument to the inclusion so that the developer is in control of this behavior. Plus perhaps a flag in the bower object that turns bottom includes on or off for all inclusions -- a default for this inclusion flag. Does that make sense? |
I just realized that this is related to the renderer (or extension) too. CSS and .ico should never be included at the bottom. So perhaps we should extend the notion of a renderer to also have knowledge about whether can be rendered at the bottom, by default "no". |
This means it's relevant to issue #34, where we also talk about the renderer infrastructure. |
See also #37 |
This issue implies we need to have renderer classes that can have a property set |
For some .js files, it's better to include them at the bottom of the html file. Do we want that feature in bowerstatic?
The text was updated successfully, but these errors were encountered: