David Scotson

At one point you're setting your table to be 531px wide, and shortly after you set the width of the content to 598px.

I would try taking those pixel width settings out and seeing what happens.

If you want to create blue pngs then you can either use imagemagick to convert the current pngs or (since you've already converted the svgs) run a script to output them all as pngs.

I once asked in a bug if Moodle HQ could share how they created the PNGs from the SVGs, but I didn't get an answer and I got the impression it might just be done by hand, so I ended up recoloring PNGs (at the time I was mostly interested in recoloring the Bootstrap Glyphicon Sprite anyway). But if such a script exists, and you've already got blue SVGs then that's another route.

Here's couple of pink examples:

https://github.com/ds125v/moodle-theme_bootstrap_renderers/blob/master/pix/pix-pink/glyphicons-halflings-pink.png?decoy

https://github.com/ds125v/moodle-theme_bootstrap_renderers/blob/master/pix/pix-pink/i/backup.png?decoy

edit: I had to add ?decoy on the end of the github links as Moodle thought they were direct links to images and a filter tried to display them.

And here's an example of the imagemagick code for recoloring an image:

http://stackoverflow.com/questions/12165304/change-the-color-of-an-image-with-imagemagick

You'd need to use "find -exec" to run the script on every png in moodle's pix folders.

I would put the Element Library in it's own github, not a full Moodle install. It shouldn't be that hard to have it work in multiple versions of Moodle, which increases it's usefulness and user/developer base.

If you could get some indication from Moodle HQ as to which way they are leaning (between the three current codebases), and what's holding it back from being included in core (in order to focus people's efforts) then that would be a good place to start.

If nothing happens (quickly) in core, can we just adopt one of the admin tools in the inked bug (there's Simon's original, Sam's rebase of Simon's, and a partial rewrite by Sam) and install it separately into our own dev Moodles.

Any of the three are better than what we have now (which is nothing), but there's plenty more to be done to cover all the common functionality in Moodle, and it's mostly very boring grunt work, nothing fancy. But the people who it saves the most time are themers so we might as well do that work together and save us all some time. It should be relatively simple to integrate that work back into whatever core decides to do.

I thought Moodle already did this via headers?

It was discussed when we started using HTML5 doctype here:
https://tracker.moodle.org/browse/MDL-34299?focusedCommentId=170566&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-170566

And Petr replied that this was already done (presumably via headers).

Checking the headers of qa.moodle.net I can see:

x-ua-compatible: "IE=edge"

So is it a case of this not working in certain situations?