BasicLTI with Moodle 2.0.4 and Internet Explorer

42 views
Skip to first unread message

ferrisoxide

unread,
Aug 8, 2011, 10:22:27 PM8/8/11
to Moodle-BLTI
Hi

Has anyone had any issues with Moodle 2.0 and Internet Explorer 8.0?
Content that works with BasicLTI under 1.9.6 comes up with what looks
like a broken link (frame is empty except for a red 'X' in the top
left hand corner).

Looking at the HTML that is generated, 2.0 and 1.9's BasicLTI seem a
bit different - the latter has a very obvious IFRAME but I can't
figure out what mechanism 2.0 is using to render the LTI content. Is
it using Javascript to load the content? If so I'm wondering if this
is failing under IE.

Any advice appreciated. Thanks in advance

-Tom

Nikolas Galanis

unread,
Aug 9, 2011, 6:42:20 AM8/9/11
to moodl...@googlegroups.com
Hi Tom,

we have only been developing BasicLTI using Firefox and occasionally Safari and rarely Chrome. It is very possible that there may be some browser incopatibilities that we have yet to detect and address.

For Moodle 2.0 we are using an object tag to display the tool due to the Moodle team's instructions to avoid using iframes in Moodle.

Sorry for the brief reply but we are all in vacation for the month of August and I am replying from the beach :)

Regards,

Nikolas

ferrisoxide

unread,
Aug 9, 2011, 7:40:20 AM8/9/11
to Moodle-BLTI
Thanks for the response Nikolas

The object tag model doesn't seem to work in Webkit-based browsers nor
in IE - at least not the way it's implemented in the Moodle 2.0
BasicLTI. We may be causing some of this ourselves it by using Flash
content, but even so we went from something that worked with Moodle
1.9.6 in all browsers to something that only works in Firefox under
2.0 and 2.1.

I've fixed the issue by reintroducing the iframe - this is in a
separate project up on Github (will post details when I get back at
work). The "fix" is really a hack - I'd rather find something a bit
more elegant, perhaps putting the <iframe> within the <object> tag so
that it can default to the iframe if the object fails. I understand
this is the built in default mechanism for <object> tags, but I have
to have a bit of a play before I'm happy. There are probably better
ways again.

I get why the Moodle crowd is pushing for <object> over <iframe>, but
any solution has to work with all the modern browsers. We'll be keen
to test as we need to support IE, Chrome and Safari - so we'll look
forward to giving you as much feedback as we can.

Again, thanks for getting in touch. Enjoy your holidays! :)

Cheers
Tom

On Aug 9, 7:42 pm, Nikolas Galanis <ngala...@gmail.com> wrote:
> Hi Tom,
>
> we have only been developing BasicLTI using Firefox and occasionally Safari
> and rarely Chrome. It is very possible that there may be some browser
> incopatibilities that we have yet to detect and address.
>
> For Moodle 2.0 we are using an object tag to display the tool due to the
> Moodle team's instructions to avoid using iframes in Moodle.
>
> Sorry for the brief reply but we are all in vacation for the month of August
> and I am replying from the beach :)
>
> Regards,
>
> Nikolas
>

ferrisoxide

unread,
Aug 9, 2011, 9:53:26 PM8/9/11
to Moodle-BLTI
FYI, our "hack" version of the BasicLTI plugin can be found here:

https://github.com/catapult-elearning/basiclti4moodle

Cheers
Tom

csev

unread,
Aug 10, 2011, 7:48:14 AM8/10/11
to moodl...@googlegroups.com
It occurs to me that once there is a copy of the blti code sitting in the Moodle trunk repository, there is no reason not to take these kinds of changes back into the basiclti4moodle repo.

We may even want to rename this module in case folks want to use this one at times in addition to the one in core because we can be more agile with this one - just thinking out loud and without understanding the cultural implications here.

/Chuck

Reply all
Reply to author
Forward
0 new messages