Voting starts in March for the Drupal Association Board election.
Our support of drupal_add_js/css is a bit superficial currently.
There are four 'modes' (drupal_add_css only has 3, but that doesn't really matter):
- setting (JS-only)
We (implicitly) say in libraries.api.php that we support all of them, but currently that's not entirely true.
Because we have to prepend the library path to filenames (type 'file'), we currently also prepend the library path to inline JS (and CSS). 'setting' currently works (it should work, at least, I haven't tried it).
'external' also works, but is not really necessary, because we check with url_is_external() for external filepaths.
So the question is, whether we want to support 'inline' and 'setting' JS/CSS. It would be most flexible, but IMO both 'inline' and 'setting' defeat the purpose of external libraries. If we don't want to support them libraries_load_files() will get a bit simpler, otherwise a bit more complex.
I will try to roll patches for both.
PASSED: [[SimpleTest]]: [MySQL] 35,079 pass(es). View
FAILED: [[SimpleTest]]: [MySQL] 32,046 pass(es), 4 fail(s), and 4 exception(es). View
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch test_js_css.patch. View
FAILED: [[SimpleTest]]: [MySQL] 32,020 pass(es), 15 fail(s), and 0 exception(es). View
FAILED: [[SimpleTest]]: [MySQL] 32,077 pass(es), 10 fail(s), and 0 exception(es). View