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
>