You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "scoped" is used as the name of the dependency, a kind of hack... and handle by the CSSResource class: CSSResource.prototype.register = function register(registry, name) { if (name === 'scoped') { registry.registerViewEngineHooks(this._scoped); } else { this._global = true; } };
Should I add a property media, to the class TemplateDepency or should I add a new property containing an object (for example named: settings) with different properties to manage other future attributes on the require element?
If we decide to add a settings property, the scoped value should be stored in it, and the as='scoped' should be deprecated, and use <require from="print.css" scoped="on"/> instead or something similar.
I'm submitting a feature request.
Some libraries provides css files for printing, and ask to add it like this:
<link href="print.css" rel="stylesheet" type="text/css" media="print" />
It should be useful to have an attribute "media" for the require tag to handle this case.
Sample of expected behavior:
<require from="print.css" media="print">
if this feature is accepted by the community, I'm ready to do the analyze of the changes and do them.
The text was updated successfully, but these errors were encountered: