When a gadget only has css files, it get a loader.load entry. In my opinion it is easy/cheap to check, if the gadget has only css files and than skip that entry, because the css should be enough to get. Thanks.
Version: unspecified
Severity: enhancement
(In reply to comment #0)
When a gadget only has css files, it get a loader.load entry. In my opinion it
is easy/cheap to check, if the gadget has only css files and than skip that
entry, because the css should be enough to get. Thanks.
Then how do you suggest the CSS actually ends up in the client ?
mw.loader requests modules in batch from load.php based on the dependency model and current last-modified timestamps from the startup module.
load.php then responses with the requested modules and their 3 components (of which some could be empty/undefined): JS function, CSS stylesheet, i18n messages. These are then unpackaged on the client (e.g. style is inserted into the <style> tag).
What is your suggestions exactly?
CSS is loaded with a <link rel="stylesheet" href="//.../load.php?debug=false&..." type="text/css" media="all" />.
There is no need for a javascript part.
I forgot about this task, but I've since fixed this. The state tracking has since been integrated with ResourceLoader.
See also: