David Scotson

A few relevant bugs:

MDL-37231 Make the new SVG icons into an icon font

MDL-40759 Use the Font Awesome icon font for all icons in Moodle

MDL-42662 Make API to use icons (or icon sets) to leverage qualities in our icon (sets) and allow BC in icon semantics

MDL-40770 Implement Icons for TinyMCE 3.*

It's worth noting that in your screenshot there's probably already 3 or 4 different methods (of different levels of cunningness) being used to give icons in different places color. So it might be possible to extend that to the currently gray ones via similar methods.

But it's a lot of work finding each of these different different ways of adding icons and coming up with workarounds.

PS the font awesome filter for icons in content is probably relevant too:

http://docs.moodle.org/25/en/FontAwesome_filter

I take it you've checked in other themes like Standard to see if the behaviour you are seeing changes?

I can't think of any reason why the Essential theme would stop a plugin from including it's own styles.css.

If you've got theme developer mode on then you should be able to see all of the plugin CSS listed individually, either directly in the source or in e.g. Firefox developer tools.

I believe the official policy in the 2.6 release notes is:

IE8 and Safari 5 are no longer fully supported. They should still work but they are not tested regularly and there might be some problems. Like most of the world's Web sites and browser producers, we encourage you to keep your browsers current to improve security and functionality while saving us valuable time. (For example see what Google is doing.)

IE6 and IE7 are not recommended for Moodle 2.6 at all. You will encounter difficulties trying to use those old browsers in today's Internet.

But you can't yet intentionally remove things that target IE6 & 7, and no date for that is set yet.

Hi Tim,

couple of questions for you:

1. What are you measuring to get that 0.33s, 0.41s and 0.36s "page-load" figure? I assume that it's how long the server is working for as it seems very quick for a full page load (we see 0.12 seconds just to download the average Moodle page and about 0.1-0.3s difference between "document interactive" and "document content loaded")

2. Do you happen to know if the "Performance Info" that Moodle can currently append to pages can be logged instead? (edit: answering my own question via Google: the MDL_PERFTOLOG setting seems to do this)

I was reading the "Mature Optimisation Handbook" that Facebook released and it suggested that logging that kind of info on every access in production was an important part of their optimization process (specifically Chapter 5. Instrumentation)

http://carlos.bueno.org/optimization/

It would probably be interesting to see that info for test runs like you describe. And actually, a third question, how are you scripting those? We've been using wget for similar stuff but maybe there's better tools out there?

Regarding the score for loading speed, did we ever figure out why it takes so much longer for Moodle to load TinyMCE (v3) than the TinyMCE demo page takes ( http://www.tinymce.com/tryit/basic.php )?

I'm guessing from the table in the wiki that the delay is still present for TinyMCE v4 in Moodle.