Making Moodle work better on #Chrome browser


I use Chrome browser for my day to day internet browsing and work, even for accessing Moodle site.  Which is why it kinda stinks that the HTMLArea text editor doesn’t function in Chrome.  There are 2 ways to get it to work though, so if you’re a Chrome and Moodle fan and want to love them both at the same time, check out these two solutions:

Post Pages - Post Inline - WIRIS

1.  The lowest tech: this solution is simple, but new to me.  It was described by Emory Maiden through the MoodleMayhem list serv while we were discussing possibilities.  Here’s the run down,

  • Open Chrome and click on “Customize and Control Google Chrome” (The wrench in the upper right).
  • Select “Extensions” from the menu and then click on “Browse the Gallery”.
  • In the search box at the top search for “IEtab”Click on the IE Tab link when it appears, it is by Blackfish Software
  • Install the extension
  • Go to into Moodle.  You will need to click on the Internet Explorer icon that is now on your tool bar in the upper right beside the Wrench icon when you want to switch to the easy editor but the fix has worked pretty well for us.  [editor’s note: this does not work on Chrome for Linux]

2.  Higher tech: change some Moodle code.  This solution is from the forums and was suggested/provided by Pall Thayer and includes two small edits to Moodle’s php files []:

step 1:
can_use_html_editor function in file /lib/moodlelib.php
line 6519 } else {
line 6520 return 1;
line 6521 }

step 2:
This will tell the HTML editor to use its ‘Gecko’ configuration for Safari and browsers that it identifies as “Mozilla < 1.3”, for instance, Chrome.
HTMLArea.checkSupportedBrowser = function() in /lib/editor/htmlarea/htmlarea.php
line 2408 //alert(“Mozilla < 1.3 Beta is not supported!\n” +
line 2409 // “I’ll try though, but it might not work.”);
line 2410 return ‘HTMLArea.is_gecko’;
line 2414 //return false;
line 2415 return ‘HTMLArea.is_gecko’;

The latter was attempted successfully by Ben Wilkoff, who mentioned “just used the hack to get HTMLArea to appear and it works great!”

There’s also the possibility of replacing HTMLArea, the default text editor in 1.X with TinyMCE (which will be the default in 2.0); but that process is admittedly more technical.

Are you a Chrome user?  Did either of these fit the bill for you?