Moodle
  1. Moodle
  2. MDL-36803

TinyMCE editor doesn't accept keyboard input on iOS6 after touch event

    Details

    • Testing Instructions:
      Hide

      Using safari on iOS and one non safari browser on iOS

      • Open a course
      • Turn editing on
      • Open a forum
      • Create a new discussion
      • Type something in TinyMCE
      • Touch, and refocus the cursor
      • Try and type again

      This should be done BOTH before and after applying the patch. You MUST make sure that you can replicate the issue (only in safari) before passing this.

      Please note that only iOS Safari seems to be affected. Other iOS browsers are not necessarily affected but need to be checked for regressions.

      Show
      Using safari on iOS and one non safari browser on iOS Open a course Turn editing on Open a forum Create a new discussion Type something in TinyMCE Touch, and refocus the cursor Try and type again This should be done BOTH before and after applying the patch. You MUST make sure that you can replicate the issue (only in safari) before passing this. Please note that only iOS Safari seems to be affected. Other iOS browsers are not necessarily affected but need to be checked for regressions.
    • Workaround:
      Hide

      Close keyboard and refocus.

      Show
      Close keyboard and refocus.
    • Affected Branches:
      MOODLE_23_STABLE, MOODLE_24_STABLE, MOODLE_25_STABLE
    • Fixed Branches:
      MOODLE_24_STABLE, MOODLE_25_STABLE
    • Pull 2.4 Branch:
      MDL-36803-m24
    • Pull 2.5 Branch:
      MDL-36803-m25
    • Pull Master Branch:
    • Story Points:
      20
    • Rank:
      52027
    • Sprint:
      FRONTEND Sprint 4

      Description

      We're seeing that TinyMCE does not allow you to continue using the keyboard after you've typed something in, and then used the magnifier to move elsewhere in the text:

      • Create a new forum post
      • Type some text (preferably something reasonably long)
      • Click elsewhere in the text to move the cursor (or try to zoom out)
      • Try and type some more content
      1. Foto.PNG
        74 kB
      2. Foto.PNG
        209 kB
      3. moodlez-moodle25.png
        305 kB
      4. moodlez-moodle26.png
        313 kB
      5. moodlez-qa_moodle_net.png
        90 kB

        Issue Links

          Activity

          Hide
          Andrew Nicols added a comment -

          This does seem to be working with the TinyMCE fiddler.

          I don't have a real iPad running iOS 6 here, but the Xcode iOS simulator does replicate the issue. I'm seeing this in 2.3 and qa.moodle.net (which is presumably running 2.4 beta).

          Looks like it's also broken on iOS 5.1

          Show
          Andrew Nicols added a comment - This does seem to be working with the TinyMCE fiddler. I don't have a real iPad running iOS 6 here, but the Xcode iOS simulator does replicate the issue. I'm seeing this in 2.3 and qa.moodle.net (which is presumably running 2.4 beta). Looks like it's also broken on iOS 5.1
          Hide
          Andrew Nicols added a comment -

          Also broken on iOS 5.0 safari.

          Show
          Andrew Nicols added a comment - Also broken on iOS 5.0 safari.
          Hide
          Andrew Nicols added a comment -

          Works on fiddle.tinymce.com with version 3.5.7, 3.5.6 (master is on 3.5.7b); and 3.5.1.1 (found in 2.3.2)

          Show
          Andrew Nicols added a comment - Works on fiddle.tinymce.com with version 3.5.7, 3.5.6 (master is on 3.5.7b); and 3.5.1.1 (found in 2.3.2)
          Hide
          Petr Škoda added a comment -

          Strange, it works fine when I edit frontapge description (admin setting) but fails when editing forum posts.

          Show
          Petr Škoda added a comment - Strange, it works fine when I edit frontapge description (admin setting) but fails when editing forum posts.
          Hide
          Petr Škoda added a comment -

          I have tried to remove the onchange validation, image and media plugins and it still breaks when adding posts.

          This looks like our problem, not upstream...

          Show
          Petr Škoda added a comment - I have tried to remove the onchange validation, image and media plugins and it still breaks when adding posts. This looks like our problem, not upstream...
          Hide
          Petr Škoda added a comment -

          wow, if I comment out the filemanager element in the forum post form it starts to work properly.

          Show
          Petr Škoda added a comment - wow, if I comment out the filemanager element in the forum post form it starts to work properly.
          Hide
          Petr Škoda added a comment -

          hmm, if I comment out "this.selectui.plug(Y.Plugin.Drag,

          {handles:['#'+this.selectnode.get('id')+' .yui3-widget-hd']}

          );" from the filemanager.js it starts to work, no idea why...

          Show
          Petr Škoda added a comment - hmm, if I comment out "this.selectui.plug(Y.Plugin.Drag, {handles:['#'+this.selectnode.get('id')+' .yui3-widget-hd']} );" from the filemanager.js it starts to work, no idea why...
          Hide
          d jackson added a comment - - edited

          yes - we are still seeing this problem. Tried downloading Chrome for iPad to see if it made any difference - but no luck. Also tried fiddle.tinymce.com like Andrew in 3.5.1.1 and it works ok here.

          So - with a bit of fiddling i found a workaround - its not perfect obviously, but it means you CAN input text after a touch event

          I could only get it to work on Chrome for iPad, not Safari. For reference our iPad is version iOS5

          1. Download Chrome for iPad - follow these instructions - http://support.google.com/chrome/bin/answer.py?hl=en&answer=2641259
          2. Go to reply to a post or another TinyMCE action. Add some text, a carriage return, then some more text
          3. Use a Touch Event to go back to your first line of text to try to add more text to this line - you will find you cannot add text
          4. To get around this, click on the enlarge TinyMCE editor button - its the Blue Screen icon next to the 'Binoculars and A B' button - all you have to do is click it to enlarge the editor, then once the editor enlarges, click it again to shrink the screen.
          5. You should now be able to input text where you wanted to. Repeat the process every time you get stuck on a Touch Event.

          Like i say - not perfect, but it will help you get the post finished

          Show
          d jackson added a comment - - edited yes - we are still seeing this problem. Tried downloading Chrome for iPad to see if it made any difference - but no luck. Also tried fiddle.tinymce.com like Andrew in 3.5.1.1 and it works ok here. So - with a bit of fiddling i found a workaround - its not perfect obviously, but it means you CAN input text after a touch event I could only get it to work on Chrome for iPad, not Safari. For reference our iPad is version iOS5 1. Download Chrome for iPad - follow these instructions - http://support.google.com/chrome/bin/answer.py?hl=en&answer=2641259 2. Go to reply to a post or another TinyMCE action. Add some text, a carriage return, then some more text 3. Use a Touch Event to go back to your first line of text to try to add more text to this line - you will find you cannot add text 4. To get around this, click on the enlarge TinyMCE editor button - its the Blue Screen icon next to the 'Binoculars and A B' button - all you have to do is click it to enlarge the editor, then once the editor enlarges, click it again to shrink the screen. 5. You should now be able to input text where you wanted to. Repeat the process every time you get stuck on a Touch Event. Like i say - not perfect, but it will help you get the post finished
          Hide
          Martin Dougiamas added a comment -

          Very urgent. Moodle is pretty useless on iOS otherwise.

          Show
          Martin Dougiamas added a comment - Very urgent. Moodle is pretty useless on iOS otherwise.
          Hide
          Martin Dougiamas added a comment -

          Is it caused by some of the new YUI3 stuff?

          Show
          Martin Dougiamas added a comment - Is it caused by some of the new YUI3 stuff?
          Hide
          Andrew Nicols added a comment -

          Hi Martin,

          I've only tried replicating this back to 2.3 so far. I'll try and replicate in 2.2.

          Petr has narrowed it down to the use of this.selectui.plug(Y.Plugin.Drag);
          this.selectui is defined in both lib/form/filemanager.js and repository/filepicker.js

          I suspect that this is unrelated to the new YUI3 stuff - it's probably a mis-configuration of (our use of) the plugin.

          Show
          Andrew Nicols added a comment - Hi Martin, I've only tried replicating this back to 2.3 so far. I'll try and replicate in 2.2. Petr has narrowed it down to the use of this.selectui.plug(Y.Plugin.Drag); this.selectui is defined in both lib/form/filemanager.js and repository/filepicker.js I suspect that this is unrelated to the new YUI3 stuff - it's probably a mis-configuration of (our use of) the plugin.
          Hide
          Martin Dougiamas added a comment -

          Sorry, I didn't mean when we added YUI3, I mean all the YUI3-based JS added recently for drag/drop and other features etc ...

          Show
          Martin Dougiamas added a comment - Sorry, I didn't mean when we added YUI3, I mean all the YUI3-based JS added recently for drag/drop and other features etc ...
          Hide
          Andrew Nicols added a comment -

          Replicated in a very basic fiddle including TinyMCE http://fiddle.tinymce.com/2Qcaab.
          The moment that you add the Y.Plugin.Drag plugin, tinymce gets upset with touch events.

          Show
          Andrew Nicols added a comment - Replicated in a very basic fiddle including TinyMCE http://fiddle.tinymce.com/2Qcaab . The moment that you add the Y.Plugin.Drag plugin, tinymce gets upset with touch events.
          Hide
          Andrew Nicols added a comment -

          Only an issue in Safari - Chrome for iPad works fine.

          Show
          Andrew Nicols added a comment - Only an issue in Safari - Chrome for iPad works fine.
          Hide
          Andrew Nicols added a comment -

          Seems to work fine on iPhone 5 with iOS 6.1.2
          iPad fails with iOS 6.1.2

          Show
          Andrew Nicols added a comment - Seems to work fine on iPhone 5 with iOS 6.1.2 iPad fails with iOS 6.1.2
          Hide
          Andrew Nicols added a comment -

          nope - iPhone too. My mistake. I must have loaded the version without Y.Plugin.Plug

          Show
          Andrew Nicols added a comment - nope - iPhone too. My mistake. I must have loaded the version without Y.Plugin.Plug
          Hide
          Andrew Nicols added a comment -

          Opened a YUI bug http://yuilibrary.com/projects/yui3/ticket/2533161

          On a side note, TinyMCE REALLY sucks on the iPad. It constantly changes focus.

          Show
          Andrew Nicols added a comment - Opened a YUI bug http://yuilibrary.com/projects/yui3/ticket/2533161 On a side note, TinyMCE REALLY sucks on the iPad. It constantly changes focus.
          Hide
          Andrew Nicols added a comment -

          I think that this is probably a TinyMCE issue. It looks like a jQuery touch start event is also affected: http://www.tinymce.com/develop/bugtracker_view.php?id=5164
          They're claiming that it's an iOS issue, but I'm not so sure.

          Show
          Andrew Nicols added a comment - I think that this is probably a TinyMCE issue. It looks like a jQuery touch start event is also affected: http://www.tinymce.com/develop/bugtracker_view.php?id=5164 They're claiming that it's an iOS issue, but I'm not so sure.
          Hide
          Carlo Gandolfi added a comment - - edited

          Just point out that TinyMCE in these examples (http://www.neele.name/pdw_toggle_toolbars/) works fine with iOS 6.1, both Chrome and Safari (no focus changes).

          I've installed pdw plugin on my Moodle 2.4 but don't work with iOS.
          Hope this help solve the bug.

          From moodle forum:
          https://moodle.org/mod/forum/discuss.php?d=224600
          https://moodle.org/mod/forum/discuss.php?d=224425

          Show
          Carlo Gandolfi added a comment - - edited Just point out that TinyMCE in these examples ( http://www.neele.name/pdw_toggle_toolbars/ ) works fine with iOS 6.1, both Chrome and Safari (no focus changes). I've installed pdw plugin on my Moodle 2.4 but don't work with iOS. Hope this help solve the bug . From moodle forum: https://moodle.org/mod/forum/discuss.php?d=224600 https://moodle.org/mod/forum/discuss.php?d=224425
          Hide
          Andrew Nicols added a comment -

          Hi Carlo,

          The issue with TinyMCE relates to the inclusion of a set of touch event listeners on the same page. Since there aren't any touch events (drag/drop) on that page, it will work.

          Andrew

          Show
          Andrew Nicols added a comment - Hi Carlo, The issue with TinyMCE relates to the inclusion of a set of touch event listeners on the same page. Since there aren't any touch events (drag/drop) on that page, it will work. Andrew
          Hide
          Petr Škoda added a comment -

          I am afraid I can not help here, sorry, reassigning back to HQ.

          Show
          Petr Škoda added a comment - I am afraid I can not help here, sorry, reassigning back to HQ.
          Hide
          Andrew Nicols added a comment -

          I think that this is probably an issue with either TinyMCE or Safari for iOS.

          We could add a wrapper around the Plugin addition to only include it if (Y.UA.ios). It's a dirty, nasty hack, and there will be places where it doesn't work (e.g. anything else on the page which uses any form of Drag + Drop).

          Show
          Andrew Nicols added a comment - I think that this is probably an issue with either TinyMCE or Safari for iOS. We could add a wrapper around the Plugin addition to only include it if (Y.UA.ios). It's a dirty, nasty hack, and there will be places where it doesn't work (e.g. anything else on the page which uses any form of Drag + Drop).
          Hide
          Petr Škoda added a comment -

          Hmm, I remember disabling the drag and drop in JS code to hide the upload stuff on ipad because I did not find a way to use it.

          +1 for some simple hack that just disables stuff non necessary on iOS

          Show
          Petr Škoda added a comment - Hmm, I remember disabling the drag and drop in JS code to hide the upload stuff on ipad because I did not find a way to use it. +1 for some simple hack that just disables stuff non necessary on iOS
          Hide
          Andrew Nicols added a comment -

          It's actually drag + drop of the filepicker - e.g. moving it around the screen.

          Show
          Andrew Nicols added a comment - It's actually drag + drop of the filepicker - e.g. moving it around the screen.
          Hide
          Martin Dougiamas added a comment -

          We totally need to keep upload on iOS

          No need for dragging the dialog around, I don't think.

          Show
          Martin Dougiamas added a comment - We totally need to keep upload on iOS No need for dragging the dialog around, I don't think.
          Hide
          Damyon Wiese added a comment -

          (Oops, grabbed wrong issue).

          Show
          Damyon Wiese added a comment - (Oops, grabbed wrong issue).
          Hide
          Ralf Krause added a comment -

          Please add the versions 2.3.7+, 2.4.4+ and 2.5+
          In these versions the iPad with iOS6 has the problems the editor.

          Show
          Ralf Krause added a comment - Please add the versions 2.3.7+, 2.4.4+ and 2.5+ In these versions the iPad with iOS6 has the problems the editor.
          Hide
          Andrew Nicols added a comment -

          Ralf Krause, we add the first version that is affected rather than all versions.
          This is likely an issue with TinyMCE rather than iOS. I'm going to test with iOS7 if I can persuade someone with a developer license...

          Show
          Andrew Nicols added a comment - Ralf Krause , we add the first version that is affected rather than all versions. This is likely an issue with TinyMCE rather than iOS. I'm going to test with iOS7 if I can persuade someone with a developer license...
          Hide
          Andrew Nicols added a comment -

          Jérôme Mouneyrac Do you think that you can look into whether this might be fixed in TinyMCE4 and about filing an iOS bug for it? You may be in a better position to do so than me.

          Cheers, A

          Show
          Andrew Nicols added a comment - Jérôme Mouneyrac Do you think that you can look into whether this might be fixed in TinyMCE4 and about filing an iOS bug for it? You may be in a better position to do so than me. Cheers, A
          Hide
          Ralf Krause added a comment -

          I don't know if there is a problem with the Moodle configuration of the TinyMCE. I found that the iPad app MoodlEZ does not show the editor. The author of the app answered to me that the problem would come from Moodle.

          Ralf

          Show
          Ralf Krause added a comment - I don't know if there is a problem with the Moodle configuration of the TinyMCE. I found that the iPad app MoodlEZ does not show the editor. The author of the app answered to me that the problem would come from Moodle. Ralf
          Hide
          Jérôme Mouneyrac added a comment - - edited

          From the tests I ran yet:
          a) tinymce on Moodle or Wordpress is not working properl on ipad 2 - iOS 6.1 / ipod touch 4 gen - iOS - I could reproduce the issues with the focus and the keyboard not accepting any new charcaters.
          b) if you go to the official demo for tinymce and try the demo 3.5.8, same version number as in Moodle master, it works fine.
          c) I remotely inspected Moodle tinymce, no js errors are displayed when the focus bugs is triggered.

          I first thought (a) it was a tinymce/iOS issue but it works on the demo (b), so it must be related to Moodle (still need to do more tests with different version). Seeing the last Wordpress version not working is not encouraging on the difficulty of the task. Also I read somewhere in the tinymce forums (can't find it anymore) that as tinymce 4 is supposed to be working well with ios devices, no more ios device effort will be done on 3.X.

          At the end it can be a good thing to go for 4.X but that may break some 3.X plugins - I remember reading a Moodle.org discussion about getting rid of tinymce and the reason evoked to keep it was because there were many plugins. So it's maybe not such a good idea yet.

          Show
          Jérôme Mouneyrac added a comment - - edited From the tests I ran yet: a) tinymce on Moodle or Wordpress is not working properl on ipad 2 - iOS 6.1 / ipod touch 4 gen - iOS - I could reproduce the issues with the focus and the keyboard not accepting any new charcaters. b) if you go to the official demo for tinymce and try the demo 3.5.8, same version number as in Moodle master, it works fine. c) I remotely inspected Moodle tinymce, no js errors are displayed when the focus bugs is triggered. I first thought (a) it was a tinymce/iOS issue but it works on the demo (b), so it must be related to Moodle (still need to do more tests with different version). Seeing the last Wordpress version not working is not encouraging on the difficulty of the task. Also I read somewhere in the tinymce forums (can't find it anymore) that as tinymce 4 is supposed to be working well with ios devices, no more ios device effort will be done on 3.X. At the end it can be a good thing to go for 4.X but that may break some 3.X plugins - I remember reading a Moodle.org discussion about getting rid of tinymce and the reason evoked to keep it was because there were many plugins. So it's maybe not such a good idea yet.
          Hide
          Martin Dougiamas added a comment - - edited

          Jerome see above about drag/drop JS. Also we decided in another bug to do TinyMCE 4 in a separate plugin.

          Show
          Martin Dougiamas added a comment - - edited Jerome see above about drag/drop JS. Also we decided in another bug to do TinyMCE 4 in a separate plugin.
          Hide
          Jérôme Mouneyrac added a comment - - edited

          Thanks Martin. Andrew, tinymce 4.0.1 still has the bug: http://fiddle.tinymce.com/Wpdaab
          I've just noticed the bug exists without using YUI: http://fiddle.tinymce.com/Wpdaab/1

          Show
          Jérôme Mouneyrac added a comment - - edited Thanks Martin. Andrew, tinymce 4.0.1 still has the bug: http://fiddle.tinymce.com/Wpdaab I've just noticed the bug exists without using YUI: http://fiddle.tinymce.com/Wpdaab/1
          Hide
          Jérôme Mouneyrac added a comment - - edited

          UX question: would it not be user friendly to display tinymce in full screen on iOS devices?

          a) moodle detects it's running on a mobile device
          b) The forms only display a readonly lookalike textaera instead of text editors. Clicking on the read only lookalike textarea display tinymce in fullscreenmode (not movable, not resizable). I'm not sure if it's technically possible (when probably can hide tinymce then unhide it on the top of the all page - we would just need some button DONE/CANCEL)

          Tackling a mobile-friendly issue might help to resolve this issue (the current full screen tinymce feature has the issue, but we might be able to implement a easier fix as the user won't touch anything else than tinymce) but also will get rid all the annoying resize, unwanted mistouch, smallish button. What do you think?

          Show
          Jérôme Mouneyrac added a comment - - edited UX question: would it not be user friendly to display tinymce in full screen on iOS devices? a) moodle detects it's running on a mobile device b) The forms only display a readonly lookalike textaera instead of text editors. Clicking on the read only lookalike textarea display tinymce in fullscreenmode (not movable, not resizable). I'm not sure if it's technically possible (when probably can hide tinymce then unhide it on the top of the all page - we would just need some button DONE/CANCEL) Tackling a mobile-friendly issue might help to resolve this issue (the current full screen tinymce feature has the issue, but we might be able to implement a easier fix as the user won't touch anything else than tinymce) but also will get rid all the annoying resize, unwanted mistouch, smallish button. What do you think?
          Hide
          Andrew Nicols added a comment -

          Jérôme Mouneyrac,

          I think that it will still represent an issue even if full screened. I do agree it would make sense to full screen it in terms of UX improvement, but any time you have drag and drop enabled on the page, and try to focus the loupe on a piece of text, you will cease to be able to enter text again.

          As I mentioned in my earlier comment, it is NOT YUI specific. The TinyMCE author suggests that it is a bug in iOS and won't look further. You can replicate this with jQuery, and no doubt others. I suspect that if you add an EventListener to some of the touch events on a basic tinymce fiddle, you'll see exactly the same issue. So it's either a bug with TinyMCE not coexisting properly with those touch events, or Safari under iOS being buggy.

          Either way, making this full screen will not fix the issue as the touch event is still present on the page regardless of whether it is full screen or not.

          Andrew

          Show
          Andrew Nicols added a comment - Jérôme Mouneyrac , I think that it will still represent an issue even if full screened. I do agree it would make sense to full screen it in terms of UX improvement, but any time you have drag and drop enabled on the page, and try to focus the loupe on a piece of text, you will cease to be able to enter text again. As I mentioned in my earlier comment, it is NOT YUI specific. The TinyMCE author suggests that it is a bug in iOS and won't look further. You can replicate this with jQuery, and no doubt others. I suspect that if you add an EventListener to some of the touch events on a basic tinymce fiddle, you'll see exactly the same issue. So it's either a bug with TinyMCE not coexisting properly with those touch events, or Safari under iOS being buggy. Either way, making this full screen will not fix the issue as the touch event is still present on the page regardless of whether it is full screen or not. Andrew
          Hide
          Jérôme Mouneyrac added a comment - - edited

          Thanks Andrew for explaining. I'll create an issue for the UX improvement for master and keep going with this one.

          Show
          Jérôme Mouneyrac added a comment - - edited Thanks Andrew for explaining. I'll create an issue for the UX improvement for master and keep going with this one.
          Hide
          Jérôme Mouneyrac added a comment - - edited

          I'll post my progress:

          I spent some time in the tinymce code
          When you change the focus and type a character:
          on desktop: the typed character is well know (onkeyup native event) and editor.getContent() return the updated content
          on iOS 6.1: the typed character is well know (onkeyup native event) and editor.getContent() return the non updated content

          I found that Dojo had the exact same bug with their editor:
          http://jsbin.com/upavuv/1/edit (http://stackoverflow.com/questions/16622684/double-clicking-on-a-div-with-contenteditable-inside-and-iframe-disables-div, I tested with the last dojo version and it still has the issue: http://jsbin.com/upavuv/13/edit

          So it could be an iOS bug or both tinymce/dojo editor have the same problem.
          PS: tinymce had zero references to touch events in its code.

          Show
          Jérôme Mouneyrac added a comment - - edited I'll post my progress: I spent some time in the tinymce code When you change the focus and type a character: on desktop: the typed character is well know (onkeyup native event) and editor.getContent() return the updated content on iOS 6.1: the typed character is well know (onkeyup native event) and editor.getContent() return the non updated content I found that Dojo had the exact same bug with their editor: http://jsbin.com/upavuv/1/edit ( http://stackoverflow.com/questions/16622684/double-clicking-on-a-div-with-contenteditable-inside-and-iframe-disables-div , I tested with the last dojo version and it still has the issue: http://jsbin.com/upavuv/13/edit So it could be an iOS bug or both tinymce/dojo editor have the same problem. PS: tinymce had zero references to touch events in its code.
          Hide
          Andrew Nicols added a comment -

          Jérôme Mouneyrac I started having a look into the TinyMCE code yesterday morning briefly, and there definitely is drag/drop code in there. They have a DragManager which listens for various drag events (not touch).

          Show
          Andrew Nicols added a comment - Jérôme Mouneyrac I started having a look into the TinyMCE code yesterday morning briefly, and there definitely is drag/drop code in there. They have a DragManager which listens for various drag events (not touch).
          Hide
          Jérôme Mouneyrac added a comment -

          Just an info on the progress with this issue:
          I found a dirty fix. Duplicated every single mouseup, mousedown, mousemove code with touchstart, touchend and touchmove in the tinymce main js. Then all works fine.
          I'm working on a cleaner solution, converting the touch events into mouse events during tinymce integration. I'm trying to add the convertion into tinymce module.js. Andrew if ever you have some time today and you want to have a quick look, it would be great. Example of touch to mouse convertion code: http://stackoverflow.com/questions/1517924/javascript-mapping-touch-events-to-mouse-events

          My main issue as been how the cache behaves specifically on iOS device (the main Moodle javascript file get screw almost every refresh when you make a change to module.js, whatever settings I set in Moodle admin or config.php). My second issue was the ios simulator that suddenly decided to not simulate touch events... Apple is a little cheeky Any tips on debugging Moodle on a iOS device is welcome (Jason mentioned to me that Chrome also does remote debugging, so I'll try tomorrow)

          cheers

          Show
          Jérôme Mouneyrac added a comment - Just an info on the progress with this issue: I found a dirty fix. Duplicated every single mouseup, mousedown, mousemove code with touchstart, touchend and touchmove in the tinymce main js. Then all works fine. I'm working on a cleaner solution, converting the touch events into mouse events during tinymce integration. I'm trying to add the convertion into tinymce module.js. Andrew if ever you have some time today and you want to have a quick look, it would be great. Example of touch to mouse convertion code: http://stackoverflow.com/questions/1517924/javascript-mapping-touch-events-to-mouse-events My main issue as been how the cache behaves specifically on iOS device (the main Moodle javascript file get screw almost every refresh when you make a change to module.js, whatever settings I set in Moodle admin or config.php). My second issue was the ios simulator that suddenly decided to not simulate touch events... Apple is a little cheeky Any tips on debugging Moodle on a iOS device is welcome (Jason mentioned to me that Chrome also does remote debugging, so I'll try tomorrow) cheers
          Hide
          Andrew Nicols added a comment -

          So what you're saying is that the iOS Safari browser does not send mouse events but does send touch events. IMO, this is correct behaviour. You're not using a Mouse after all.

          If you're duplicating events, that's bad... we shouldn't be doing that as it can mean that things are triggered twice.

          I'll be interested to see what changes you have when you get a chance to push them.

          Andrew

          Show
          Andrew Nicols added a comment - So what you're saying is that the iOS Safari browser does not send mouse events but does send touch events. IMO, this is correct behaviour. You're not using a Mouse after all. If you're duplicating events, that's bad... we shouldn't be doing that as it can mean that things are triggered twice. I'll be interested to see what changes you have when you get a chance to push them. Andrew
          Hide
          Jérôme Mouneyrac added a comment -

          Yes that's it. First touch on tinymce, iOS does send a mousedown. But all others are touchstart.

          Show
          Jérôme Mouneyrac added a comment - Yes that's it. First touch on tinymce, iOS does send a mousedown. But all others are touchstart.
          Hide
          Andrew Nicols added a comment -

          Fabulous. I guess TinyMCE does some bizarre testing which breaks. Have you got something which proves the iOS idiocy of that?

          Show
          Andrew Nicols added a comment - Fabulous. I guess TinyMCE does some bizarre testing which breaks. Have you got something which proves the iOS idiocy of that?
          Hide
          Jérôme Mouneyrac added a comment -

          add console.log('Event type:' + evt.type); in the native handler function of tinymce:

          tinymce.Editor.prototype.bindNativeEvents = function() {
          ...
          function eventHandler(evt, args) {
          console.log('Event type:' + evt.type);
          

          Then test on an iOS device 6.X.

          Show
          Jérôme Mouneyrac added a comment - add console.log('Event type:' + evt.type); in the native handler function of tinymce: tinymce.Editor.prototype.bindNativeEvents = function() { ... function eventHandler(evt, args) { console.log('Event type:' + evt.type); Then test on an iOS device 6.X.
          Hide
          Damyon Wiese added a comment -

          Hi Jerome - just from reading on the web - it looks like this might be worth a try:

          http://developer.apple.com/library/IOS/#documentation/AppleApplications/Reference/SafariWebContent/HandlingEvents/HandlingEvents.html#//apple_ref/doc/uid/TP40006511-SW6

          The default behavior of Safari on iOS can interfere with your application’s custom multi-touch and gesture input. You can disable the default browser behavior by sending the preventDefault message to the event object.

          For example, to prevent scrolling on an element in iOS 2.0, implement the touchmove and touchstart event handlers as follows :

          function touchMove(event)

          { // Prevent scrolling on this element event.preventDefault(); ... }
          Show
          Damyon Wiese added a comment - Hi Jerome - just from reading on the web - it looks like this might be worth a try: http://developer.apple.com/library/IOS/#documentation/AppleApplications/Reference/SafariWebContent/HandlingEvents/HandlingEvents.html#//apple_ref/doc/uid/TP40006511-SW6 The default behavior of Safari on iOS can interfere with your application’s custom multi-touch and gesture input. You can disable the default browser behavior by sending the preventDefault message to the event object. For example, to prevent scrolling on an element in iOS 2.0, implement the touchmove and touchstart event handlers as follows : function touchMove(event) { // Prevent scrolling on this element event.preventDefault(); ... }
          Hide
          Jérôme Mouneyrac added a comment -

          Argh, I actually don't even have a dirty solution, I had the drag and drop commented, and some caching problem with the iPad made me think the issue came from tinymce not handling touchstart. Actually I come to the same conclusion than Andrew - when YUI3 drag and drop is enabled (for example on the filemanager), then a touchstart/touchend is triggered, and somehow it causes this issue.

          Show
          Jérôme Mouneyrac added a comment - Argh, I actually don't even have a dirty solution, I had the drag and drop commented, and some caching problem with the iPad made me think the issue came from tinymce not handling touchstart. Actually I come to the same conclusion than Andrew - when YUI3 drag and drop is enabled (for example on the filemanager), then a touchstart/touchend is triggered, and somehow it causes this issue.
          Hide
          Andrew Nicols added a comment -

          I think we need to raise this with Apple. I got nowhere with the iOS Safari dev tools at the time and ran out of time to look into it.

          Show
          Andrew Nicols added a comment - I think we need to raise this with Apple. I got nowhere with the iOS Safari dev tools at the time and ran out of time to look into it.
          Hide
          Damyon Wiese added a comment -

          What about disabling drag and drop on ios safari?

          Show
          Damyon Wiese added a comment - What about disabling drag and drop on ios safari?
          Hide
          Jérôme Mouneyrac added a comment - - edited

          Just to inform about the status:
          if you comment all Y.Plugin.Drag in Moodle code and you do the following test:
          Go to course > Edit settings
          Then it works.

          Now you just "Turn editing on" and it doesn't work again. I try to disable drag and drop in moodle but it's not easy task. Note that even with AJAX disable in Moodle, there is still a bug. Note you can still move blocks around when AJAX is disabled. I didn't success to fully disable drag and drop of blocks so I still think it's where the last problem is.

          I really would appreciate some help... this bug needs to be fixed and I have quite some issues to find a solution (I think my brain is fried with this issue)

          Show
          Jérôme Mouneyrac added a comment - - edited Just to inform about the status: if you comment all Y.Plugin.Drag in Moodle code and you do the following test: Go to course > Edit settings Then it works. Now you just "Turn editing on" and it doesn't work again. I try to disable drag and drop in moodle but it's not easy task. Note that even with AJAX disable in Moodle, there is still a bug. Note you can still move blocks around when AJAX is disabled. I didn't success to fully disable drag and drop of blocks so I still think it's where the last problem is. I really would appreciate some help... this bug needs to be fixed and I have quite some issues to find a solution (I think my brain is fried with this issue)
          Hide
          Jérôme Mouneyrac added a comment - - edited

          A suggestion that has been mentioned by several persons: we could use Damyon's new html editor (https://moodle.org/plugins/view.php?plugin=editor_contenteditable&moodle_version=13) when Moodle detects iOS. Some benefits:

          • it's much faster than tinymce on mobile.
          • you can touch the editor buttons without having to zoom all the time and hoping to not press the wrong button.
          • tinymce is currently not working properly on iOS anyway. The above issues, this bug, the buttons that are not toggled off once touched...

          From asking Damyon, the only things we will be losing with his editor are the mathematic/table features. But are these features really used on iOS knowing that tinymce is not usable?

          Please share your opinion (course creators, teachers, students, admins, devs...).

          PS: can we install it on demo.moodle.net or another online test site so people could try it?

          Show
          Jérôme Mouneyrac added a comment - - edited A suggestion that has been mentioned by several persons: we could use Damyon's new html editor ( https://moodle.org/plugins/view.php?plugin=editor_contenteditable&moodle_version=13 ) when Moodle detects iOS. Some benefits: it's much faster than tinymce on mobile. you can touch the editor buttons without having to zoom all the time and hoping to not press the wrong button. tinymce is currently not working properly on iOS anyway. The above issues, this bug, the buttons that are not toggled off once touched... From asking Damyon, the only things we will be losing with his editor are the mathematic/table features. But are these features really used on iOS knowing that tinymce is not usable? Please share your opinion (course creators, teachers, students, admins, devs...). PS: can we install it on demo.moodle.net or another online test site so people could try it?
          Hide
          Damyon Wiese added a comment -

          +1 from me!

          Show
          Damyon Wiese added a comment - +1 from me!
          Hide
          Damyon Wiese added a comment -

          We discussed this in scrum, and given the amount of time spent on this issue so far - it would be better to focus on providing an alternative editor for iOS that works correctly (see linked issue).

          Show
          Damyon Wiese added a comment - We discussed this in scrum, and given the amount of time spent on this issue so far - it would be better to focus on providing an alternative editor for iOS that works correctly (see linked issue).
          Hide
          Jérôme Mouneyrac added a comment -

          As talked in the scrumm meeting we disable tinymce on iOS as it's slow and not usable.

          Show
          Jérôme Mouneyrac added a comment - As talked in the scrumm meeting we disable tinymce on iOS as it's slow and not usable.
          Hide
          Andrew Davis added a comment -

          I dont see how it could fail but expand the testing instructions to check that tinymce still functions on non-iOS devices.

          It would probably be worthwhile to create an MDL for a future Moodle release to come back and verify if there are still problems with tinymce + iOS. For all we know new versions of iOS and tinymce may fix this for us so it would be worth checking in the future.

          Otherwise, submit for integration whenever you are ready.

          Show
          Andrew Davis added a comment - I dont see how it could fail but expand the testing instructions to check that tinymce still functions on non-iOS devices. It would probably be worthwhile to create an MDL for a future Moodle release to come back and verify if there are still problems with tinymce + iOS. For all we know new versions of iOS and tinymce may fix this for us so it would be worth checking in the future. Otherwise, submit for integration whenever you are ready.
          Hide
          Martin Dougiamas added a comment -

          Guys don't just test new text fields. What happens when someone tries to edit an existing HTML text on iOS? Are they going to see raw HTML now?

          Show
          Martin Dougiamas added a comment - Guys don't just test new text fields. What happens when someone tries to edit an existing HTML text on iOS? Are they going to see raw HTML now?
          Hide
          Martin Dougiamas added a comment - - edited

          Also can I have confirmation this original JS conflict issue

          • does not affect non-iOS platforms.
          • DOES affect all iOS browsers (Chrome etc)
          Show
          Martin Dougiamas added a comment - - edited Also can I have confirmation this original JS conflict issue does not affect non-iOS platforms. DOES affect all iOS browsers (Chrome etc)
          Hide
          Jérôme Mouneyrac added a comment -
          Show
          Jérôme Mouneyrac added a comment - it affects Safari and Chrome on iOS (6 on iPad 2). it doesn't affect Chrome on Android (4.2 on Nexus 4). when someone tries to edit an existing html text on iOS with the patch, Moodle displays the html code in the default plain editor. So if we don't integrate Damyon's editor, it is as bad as having the bug. i.e. "non tech people are unable to edit a text as the text is full of html" VERSUS "people are unable to type the text except if they know about the workaround". if you want to help with this issue, the point where I am is explained there: https://tracker.moodle.org/browse/MDL-36803?focusedCommentId=237403&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-237403
          Hide
          Andrew Davis added a comment -

          Do we simply want to park this issue until MDL-41098 is integrated so we can fall back to the new editor?

          Show
          Andrew Davis added a comment - Do we simply want to park this issue until MDL-41098 is integrated so we can fall back to the new editor?
          Hide
          Ralf Krause added a comment -

          Hi,

          did anybody test the new TinyMCE 4.0.3 with Moodle? The current versions of Moodle 2.5.1+ and Moodle 2.6dev are using TinyMCE 3.5.8. In Moodle 2.4.5+ I found TinyMCE 3.5.7b.

          I hope you will fix the problem very soon because a lot of schools will start with iPad classes. There are classes in primary schools ... these children will use Moodle as a social network in their schools want to write. They want to use different fonts, they want to change the font size and the font color.

          If these classes can't use a simple text editor to do all these things they will not use Moodle.

          Ralf

          Show
          Ralf Krause added a comment - Hi, did anybody test the new TinyMCE 4.0.3 with Moodle? The current versions of Moodle 2.5.1+ and Moodle 2.6dev are using TinyMCE 3.5.8. In Moodle 2.4.5+ I found TinyMCE 3.5.7b. I hope you will fix the problem very soon because a lot of schools will start with iPad classes. There are classes in primary schools ... these children will use Moodle as a social network in their schools want to write. They want to use different fonts, they want to change the font size and the font color. If these classes can't use a simple text editor to do all these things they will not use Moodle. Ralf
          Hide
          Jérôme Mouneyrac added a comment - - edited

          I created MDL-41260 to disable tinymce on iOS as we talked about it in the scrum meeting. From what we concluded in the scrum meeting Damyon's editor will be a lighter editor working fine on mobile. It will not have all tinymce features.

          Show
          Jérôme Mouneyrac added a comment - - edited I created MDL-41260 to disable tinymce on iOS as we talked about it in the scrum meeting. From what we concluded in the scrum meeting Damyon's editor will be a lighter editor working fine on mobile. It will not have all tinymce features.
          Hide
          Martin Dougiamas added a comment -

          As there seems to be a very small doubt that this is truly the only solution, I'd like it if I could get another person to have a good look.

          Andrew Nicols are you able to dig into this for a couple of hours this week? At this stage it would preferable if we can find some hack that makes TinyMCE work on iOS (ie gets around the conflict with drag/drop YUI code).

          This would not necessarily prevent Damyon's editor landing for people to use optionally, but it would make the upgrade less urgent and wierd.

          Show
          Martin Dougiamas added a comment - As there seems to be a very small doubt that this is truly the only solution, I'd like it if I could get another person to have a good look. Andrew Nicols are you able to dig into this for a couple of hours this week? At this stage it would preferable if we can find some hack that makes TinyMCE work on iOS (ie gets around the conflict with drag/drop YUI code). This would not necessarily prevent Damyon's editor landing for people to use optionally, but it would make the upgrade less urgent and wierd.
          Hide
          Andrew Nicols added a comment -

          I'm taking another look at this now. I'm currently trying to replicate against a couple of fiddles:

          Frustratingly, I'm struggling to replicate it on my phone now and don't have my iPad with me this week.

          I'm sometimes able to replicate this issue with the iPhone simulator using an iPad on 6.1. Just installing some of the older simulators to try and replicate on there.

          Both of these are just stock TinyMCE examples with a Y.Plugin.Drag added to the page as before. The same fiddle on 3.5.8 was previously demonstrating the issue so I'm confused as to why it no longer does.

          Show
          Andrew Nicols added a comment - I'm taking another look at this now. I'm currently trying to replicate against a couple of fiddles: http://fiddle.tinymce.com/Mwdaab - TinyMCE edge http://fiddle.tinymce.com/Nwdaab - TinyMCE 3.5.8 Frustratingly, I'm struggling to replicate it on my phone now and don't have my iPad with me this week. I'm sometimes able to replicate this issue with the iPhone simulator using an iPad on 6.1. Just installing some of the older simulators to try and replicate on there. Both of these are just stock TinyMCE examples with a Y.Plugin.Drag added to the page as before. The same fiddle on 3.5.8 was previously demonstrating the issue so I'm confused as to why it no longer does.
          Hide
          Andrew Nicols added a comment -

          Okay, so with a stupidly basic contenteditable body in an iframe, as soon as we add any kind of touchstart event handler, this breaks on Safari.

          Try http://sandpit.andrewrn.co.uk/tiny/basic.html for example.

          Show
          Andrew Nicols added a comment - Okay, so with a stupidly basic contenteditable body in an iframe, as soon as we add any kind of touchstart event handler, this breaks on Safari. Try http://sandpit.andrewrn.co.uk/tiny/basic.html for example.
          Hide
          Andrew Nicols added a comment -

          A similar issue described at http://stackoverflow.com/questions/7997327/touchmove-event-in-safari-ios5-ipad-disables-contenteditable-any-workaround

          It looks like the touchstart event causes a loss of focus on the contenteditable which isn't wholly reflected in the UI.

          Not sure what the best fix is yet.

          Show
          Andrew Nicols added a comment - A similar issue described at http://stackoverflow.com/questions/7997327/touchmove-event-in-safari-ios5-ipad-disables-contenteditable-any-workaround It looks like the touchstart event causes a loss of focus on the contenteditable which isn't wholly reflected in the UI. Not sure what the best fix is yet.
          Hide
          Damyon Wiese added a comment -

          Aha - so my editor doesn't break because it doesn't use iframes.

          Show
          Damyon Wiese added a comment - Aha - so my editor doesn't break because it doesn't use iframes.
          Hide
          Andrew Nicols added a comment -
          Show
          Andrew Nicols added a comment - Damyon Wiese Apparently that is the case - see http://sandpit.andrewrn.co.uk/tiny/noframe.html
          Hide
          Andrew Nicols added a comment -

          I've opened rdar://14773810 on the Apple bug tracker. I don't think it's possible to make the bug public sadly.

          Show
          Andrew Nicols added a comment - I've opened rdar://14773810 on the Apple bug tracker. I don't think it's possible to make the bug public sadly.
          Hide
          Andrew Nicols added a comment -

          Adding the following to the editor's init seems to work around the issue:

              setup: function(editor) {
                  editor.onPostRender.add(function(ed) {
                      ed.contentDocument.addEventListener('keydown', function() {
                          ed.contentWindow.focus();
                      });
                  });
              }
          
          Show
          Andrew Nicols added a comment - Adding the following to the editor's init seems to work around the issue: setup: function(editor) { editor.onPostRender.add(function(ed) { ed.contentDocument.addEventListener('keydown', function() { ed.contentWindow.focus(); }); }); }
          Hide
          Andrew Nicols added a comment -

          I've updated the patch as per my previous comment.
          I've tested this using:

          • the iPhone Simulator with an iPad on 6.1.
          • the iPhone Simulator with an iPad on 5.1.
          • the iPhone Simulator with an iPhone 5 on 6.1.
          • the iPhone Simulator with an iPhone 5 on 5.1.
          • iPhone5 on 6.1.

          If others could please test this, that would be much appreciated. Please could you confirm first that it is indeed broken without the patch, and that the patch fixes your woes.

          Show
          Andrew Nicols added a comment - I've updated the patch as per my previous comment. I've tested this using: the iPhone Simulator with an iPad on 6.1. the iPhone Simulator with an iPad on 5.1. the iPhone Simulator with an iPhone 5 on 6.1. the iPhone Simulator with an iPhone 5 on 5.1. iPhone5 on 6.1. If others could please test this, that would be much appreciated. Please could you confirm first that it is indeed broken without the patch, and that the patch fixes your woes.
          Hide
          Andrew Nicols added a comment -

          I'll add stable branch commits once others have tested this fix works as expected.

          Show
          Andrew Nicols added a comment - I'll add stable branch commits once others have tested this fix works as expected.
          Hide
          Martin Dougiamas added a comment -

          Yay! Amazing job, Andrew, thanks!

          Please let's test it on everything ASAP and if good, backport to every stable branch there is.

          Testers, watch for caching!

          Show
          Martin Dougiamas added a comment - Yay! Amazing job, Andrew, thanks! Please let's test it on everything ASAP and if good, backport to every stable branch there is. Testers, watch for caching!
          Hide
          Jérôme Mouneyrac added a comment - - edited

          Thanks a lot Andrew! It works great on iPad. It also fixes most of the issue on iPod Touch (4th gen iOS 6) / iOS simulator. The only thing left is that on these devices, you can not change the caret position (you can do it on the tinymce demo).
          Otherwise we don't need the Y.UA.Safari test as it would skip chrome and other iOS browsers.

          Show
          Jérôme Mouneyrac added a comment - - edited Thanks a lot Andrew! It works great on iPad. It also fixes most of the issue on iPod Touch (4th gen iOS 6) / iOS simulator. The only thing left is that on these devices, you can not change the caret position (you can do it on the tinymce demo). Otherwise we don't need the Y.UA.Safari test as it would skip chrome and other iOS browsers.
          Hide
          Andrew Nicols added a comment -

          Hi Jérôme Mouneyrac,

          In my testing, the other iOS browsers which I tested did not exhibit the issue. That said, since all browsers in iOS are based on Safari, there is a potential for this to affect any iOS browser therefore I will remove the restriction.

          I'm not sure what you mean by not being able to change the caret location. I can refocus the loupe and the caret moves correctly on all of the devices that I've tested against.

          Can you please list the devices + versions that you've tested with?

          Cheers,

          Andrew

          Show
          Andrew Nicols added a comment - Hi Jérôme Mouneyrac , In my testing, the other iOS browsers which I tested did not exhibit the issue. That said, since all browsers in iOS are based on Safari, there is a potential for this to affect any iOS browser therefore I will remove the restriction. I'm not sure what you mean by not being able to change the caret location. I can refocus the loupe and the caret moves correctly on all of the devices that I've tested against. Can you please list the devices + versions that you've tested with? Cheers, Andrew
          Hide
          Jérôme Mouneyrac added a comment -

          It doesn't work on iPod Touch 4th Gen - iOS 6.1.3, iPhone 5 iOS7 and iOS iPhone simulator. Refocussing the loupe (long press) does work, it's when you do a single tap (it's what most people will do I suppose) that the caret doesn't move (but it does on tinymce demo). It works well on iPad 2 - iOS 6.

          Show
          Jérôme Mouneyrac added a comment - It doesn't work on iPod Touch 4th Gen - iOS 6.1.3, iPhone 5 iOS7 and iOS iPhone simulator. Refocussing the loupe (long press) does work, it's when you do a single tap (it's what most people will do I suppose) that the caret doesn't move (but it does on tinymce demo). It works well on iPad 2 - iOS 6.
          Hide
          Stephen McFarlane added a comment -

          Hi guys (newbie),
          Running Moodle 2.5.1 on iPad 3 (iOS 6.3).

          I have a few devices here so I can test but not sure on repro steps. Is it only in the forums that error occurs? Cannot repro in Online Text assignment. Cursor works fine, text insertion follows nicely, refocus works fine. Can test on...

          iPad 2
          iPad Mini
          iPad 3
          iPhone 5

          I work in a school that uses iOS.

          Cheers,
          Steve

          Show
          Stephen McFarlane added a comment - Hi guys (newbie), Running Moodle 2.5.1 on iPad 3 (iOS 6.3). I have a few devices here so I can test but not sure on repro steps. Is it only in the forums that error occurs? Cannot repro in Online Text assignment. Cursor works fine, text insertion follows nicely, refocus works fine. Can test on... iPad 2 iPad Mini iPad 3 iPhone 5 I work in a school that uses iOS. Cheers, Steve
          Hide
          Jérôme Mouneyrac added a comment - - edited

          Thanks Stephen. Yes more testing would be good.

          Steps:

          • connect as admin or teacher
          • go to a course. Turn editing on.
          • Edit Course settings
          • in the description enter:
            "This is the beginning of the desc...

          this is the end of the desc."

          • now single tap between the text. Your caret should have move where you tapped, you should be able to add more text there.

          +1 to send Andrew's fix to integration as it fixes the issue on iPad, I'll create a different issue for the iPhone. Is that ok?

          Show
          Jérôme Mouneyrac added a comment - - edited Thanks Stephen. Yes more testing would be good. Steps: connect as admin or teacher go to a course. Turn editing on. Edit Course settings in the description enter: "This is the beginning of the desc... this is the end of the desc." now single tap between the text. Your caret should have move where you tapped, you should be able to add more text there. +1 to send Andrew's fix to integration as it fixes the issue on iPad, I'll create a different issue for the iPhone. Is that ok?
          Hide
          Andrew Nicols added a comment -

          Yup - the loupe works, but not single taps. Thanks Jerome. I'd say that it could be a separate bug (yay) since it only affects iPod and iPhones but not iPads.

          I still can't believe how stupid and niche this issue is, and that it only affects iframed contenteditables. I wonder if there's any way to raise this to Apple in time for iOS7 release. I don't have an Apple developer account, or access to iOS7 beta. I know some of you guys do (Martin Dougiamas, Dan Poltawski, Jérôme Mouneyrac) and I wonder if there's any way we can highlight this as being a bug in the beta somehow?

          Show
          Andrew Nicols added a comment - Yup - the loupe works, but not single taps. Thanks Jerome. I'd say that it could be a separate bug (yay) since it only affects iPod and iPhones but not iPads. I still can't believe how stupid and niche this issue is, and that it only affects iframed contenteditables. I wonder if there's any way to raise this to Apple in time for iOS7 release. I don't have an Apple developer account, or access to iOS7 beta. I know some of you guys do ( Martin Dougiamas , Dan Poltawski , Jérôme Mouneyrac ) and I wonder if there's any way we can highlight this as being a bug in the beta somehow?
          Hide
          Andrew Nicols added a comment -

          Hi, Stephen McFarlane

          The issue only occurs where a TinyMCE editor is present at the same time as some kind of Drag and Drop system. As a result, this doesn't affect a majority of the instances, but it does affect any time where you have a TinyMCE editor present at the same time as a filepicker because the filepicker plugs Drag/Drop to allow you to move the dialogue.

          An example of such a location is when adding a new forum post.

          I'll see if I can put together a public Moodle with the fix applied for people to test against. If you can confirm that you can replicate the issue that would be a help in the mean time.

          Cheers,

          Andrew

          Show
          Andrew Nicols added a comment - Hi, Stephen McFarlane The issue only occurs where a TinyMCE editor is present at the same time as some kind of Drag and Drop system. As a result, this doesn't affect a majority of the instances, but it does affect any time where you have a TinyMCE editor present at the same time as a filepicker because the filepicker plugs Drag/Drop to allow you to move the dialogue. An example of such a location is when adding a new forum post. I'll see if I can put together a public Moodle with the fix applied for people to test against. If you can confirm that you can replicate the issue that would be a help in the mean time. Cheers, Andrew
          Hide
          Andrew Nicols added a comment -

          I'll put the backport branches together at lunch time (3 hours away), and remove the Safari test.
          I'll see if I can put together a temporary testing Moodle for people to test against. I think that the evidence so far suggests that these changes do resolve the issue for a majority of devices.

          Show
          Andrew Nicols added a comment - I'll put the backport branches together at lunch time (3 hours away), and remove the Safari test. I'll see if I can put together a temporary testing Moodle for people to test against. I think that the evidence so far suggests that these changes do resolve the issue for a majority of devices.
          Hide
          Stephen McFarlane added a comment -

          Hey,

          Moodle 2.5.1
          Logged in as admin

          iPad 2 running iOS 6.3 using Safari - Yes, error reproduces
          iPad Mini running iOS 6.3 using Safari - Yes, error reproduces
          iPhone 5 running iOS 6.3 using Safari - Yes, error reproduces
          iPad 3 running iOS 6.3 using Safari - Yes, error reproduces

          If there's a patch or a URL with a patch applied send it on and I'll retest.

          Steve

          Show
          Stephen McFarlane added a comment - Hey, Moodle 2.5.1 Logged in as admin iPad 2 running iOS 6.3 using Safari - Yes, error reproduces iPad Mini running iOS 6.3 using Safari - Yes, error reproduces iPhone 5 running iOS 6.3 using Safari - Yes, error reproduces iPad 3 running iOS 6.3 using Safari - Yes, error reproduces If there's a patch or a URL with a patch applied send it on and I'll retest. Steve
          Hide
          Dan Poltawski added a comment -

          Hi Andrew a bug reported to apple is best you can do. Altjough i'd imagine this corresponds to a webkit bug somehow.

          Show
          Dan Poltawski added a comment - Hi Andrew a bug reported to apple is best you can do. Altjough i'd imagine this corresponds to a webkit bug somehow.
          Hide
          Stephen McFarlane added a comment -

          Feedback for non devs: http://www.apple.com/feedback/safari.html
          Steve

          Show
          Stephen McFarlane added a comment - Feedback for non devs: http://www.apple.com/feedback/safari.html Steve
          Hide
          Andrew Nicols added a comment -

          Cheers Dan Poltawski. It could well be a webkit bug, but it's difficult to tell which way around it would be.

          Stephen McFarlane Handy - didn't know about that one. I've reported the issue to Apple in rdar://14773810 already which is probably a better location for it.

          Show
          Andrew Nicols added a comment - Cheers Dan Poltawski . It could well be a webkit bug, but it's difficult to tell which way around it would be. Stephen McFarlane Handy - didn't know about that one. I've reported the issue to Apple in rdar://14773810 already which is probably a better location for it.
          Hide
          Dan Poltawski added a comment -

          Andrew if its present on iOS6, could you copy the bug report to http://openradar.appspot.com/ ?

          (BTW I reported a security bug in iOS Safari and it probably took over 6 months to get fixed, so I wouldn't hold out hope of a rapid resolution).

          Show
          Dan Poltawski added a comment - Andrew if its present on iOS6, could you copy the bug report to http://openradar.appspot.com/ ? (BTW I reported a security bug in iOS Safari and it probably took over 6 months to get fixed, so I wouldn't hold out hope of a rapid resolution).
          Hide
          Andrew Nicols added a comment -

          Already done Dan Poltawski - http://openradar.appspot.com/radar?id=4896606314823680

          Painful to use though - is there no way of copying info in automagically from the bug reporter?

          Show
          Andrew Nicols added a comment - Already done Dan Poltawski - http://openradar.appspot.com/radar?id=4896606314823680 Painful to use though - is there no way of copying info in automagically from the bug reporter?
          Hide
          Moxiecode Systems AB added a comment -

          Nice that you guys managed to figure out that it was a focus problem. I've added a fix for it now for TinyMCE 4.x see: https://github.com/tinymce/tinymce/commit/19946dbbad203788b79395da6c3fb645022214a4

          It also detects when this focus issue occurs and only restores focus back into the iframe when needed. Seems to work fine on iOS 6 will do further testing on other iOS versions.

          Show
          Moxiecode Systems AB added a comment - Nice that you guys managed to figure out that it was a focus problem. I've added a fix for it now for TinyMCE 4.x see: https://github.com/tinymce/tinymce/commit/19946dbbad203788b79395da6c3fb645022214a4 It also detects when this focus issue occurs and only restores focus back into the iframe when needed. Seems to work fine on iOS 6 will do further testing on other iOS versions.
          Hide
          Andrew Nicols added a comment -

          Awesome, thanks Moxiecode Systems AB.

          We'll have to put an issue in ou tracker to remove our workaround when we upgrade to TinyMCE 4.X

          Show
          Andrew Nicols added a comment - Awesome, thanks Moxiecode Systems AB . We'll have to put an issue in ou tracker to remove our workaround when we upgrade to TinyMCE 4.X
          Hide
          Andrew Nicols added a comment -

          Huzzah - a little later than expected, but bugfix branches for all stable versions currently in support. I've also provided a fix for 2.3 since it's also in Security support and Martin Dougiamas said he'd like as many versions as possible. I shall let Integrators make the call.

          I've taken out the Safari check now too.

          Show
          Andrew Nicols added a comment - Huzzah - a little later than expected, but bugfix branches for all stable versions currently in support. I've also provided a fix for 2.3 since it's also in Security support and Martin Dougiamas said he'd like as many versions as possible. I shall let Integrators make the call. I've taken out the Safari check now too.
          Hide
          Andrew Nicols added a comment -

          As promised, http://sandpit.andrewrn.co.uk/36803/mod/forum/post.php?forum=2

          Username: demo
          Password: Password1!

          This demo site will disappear early next week.

          Show
          Andrew Nicols added a comment - As promised, http://sandpit.andrewrn.co.uk/36803/mod/forum/post.php?forum=2 Username: demo Password: Password1! This demo site will disappear early next week.
          Hide
          Jérôme Mouneyrac added a comment -

          Thanks Andrew. I created an issue for the left issue: MDL-41328

          Show
          Jérôme Mouneyrac added a comment - Thanks Andrew. I created an issue for the left issue: MDL-41328
          Hide
          Ralf Krause added a comment -

          Great work! I tested Andrew's demo forum with Safari on OS X 10.8.4 and with Safari on iOS 6.1.3. Both are working fine!!

          The problem was writing in the editor with Safari on iOS 6. So I wrote some words on my iPad 2. I could write the text and I could click anywhere else and come back to the text. It was possible to set the cursor back in the text to correct a word or to format a text part. I tested to click outside the editor. I made the editor bigger and smaller. I added a picture and set some picture options. Everything seems to be okay.

          I started a test with the app MoodlEZ. This app is very useful to upload files from other apps. If you write a text in a text editor and you want to upload it in Moodle then you need an app like MoodlEZ. MoodlEZ did not show the editor in the past ... and now it works!!

          It looks fine!

          Ralf

          Show
          Ralf Krause added a comment - Great work! I tested Andrew's demo forum with Safari on OS X 10.8.4 and with Safari on iOS 6.1.3. Both are working fine!! The problem was writing in the editor with Safari on iOS 6. So I wrote some words on my iPad 2. I could write the text and I could click anywhere else and come back to the text. It was possible to set the cursor back in the text to correct a word or to format a text part. I tested to click outside the editor. I made the editor bigger and smaller. I added a picture and set some picture options. Everything seems to be okay. I started a test with the app MoodlEZ. This app is very useful to upload files from other apps. If you write a text in a text editor and you want to upload it in Moodle then you need an app like MoodlEZ. MoodlEZ did not show the editor in the past ... and now it works!! It looks fine! Ralf
          Hide
          Ralf Krause added a comment -

          The editor in Safari on iOS 6.1.3 with an iPad 2.

          Show
          Ralf Krause added a comment - The editor in Safari on iOS 6.1.3 with an iPad 2.
          Hide
          Ralf Krause added a comment -

          The editor in MoodlEZ on iOS 6.1.3 with an iPad 2.

          Show
          Ralf Krause added a comment - The editor in MoodlEZ on iOS 6.1.3 with an iPad 2.
          Hide
          Stephen McFarlane added a comment -

          Hi Andrew,
          I am still seeing issues here Andrew on iPhone 5 and iPad Mini (both iOS 6.3, both running Safari)
          While I can move the caret (cursor) to a new point and enter text, I cannot get focus on a piece of text by single or double clicking it.
          I deleted my cache before visiting your URL just to be sure.
          Steve

          Show
          Stephen McFarlane added a comment - Hi Andrew, I am still seeing issues here Andrew on iPhone 5 and iPad Mini (both iOS 6.3, both running Safari) While I can move the caret (cursor) to a new point and enter text, I cannot get focus on a piece of text by single or double clicking it. I deleted my cache before visiting your URL just to be sure. Steve
          Hide
          Colin Chambers added a comment -

          Hi guys,
          We have a related issue with our superscript plugin for tinymce. I found the reason but got dragged away before I found a fix. Thought it might be relevant to this issue. The tinymce button hover status is not removed on ipad.

          It's not a fix but might be useful. I tried reading all the comments but there are so many I thought I'd just share. I know this is a drag and drop issue but you mention tinymce and ios. Since the hover state is the issue for us it could be the issue for you.

          The lesson. I don't think webkit or tinymce have figured out hover and touch on mobile devices yet.

          Show
          Colin Chambers added a comment - Hi guys, We have a related issue with our superscript plugin for tinymce. I found the reason but got dragged away before I found a fix. Thought it might be relevant to this issue. The tinymce button hover status is not removed on ipad . It's not a fix but might be useful. I tried reading all the comments but there are so many I thought I'd just share. I know this is a drag and drop issue but you mention tinymce and ios. Since the hover state is the issue for us it could be the issue for you. The lesson. I don't think webkit or tinymce have figured out hover and touch on mobile devices yet.
          Hide
          Andrew Nicols added a comment -

          Stephen McFarlane the issue you're describing is unrelated to this one - Jerome raised a similar issue in MDL-41328

          Colin Chambers Thanks for sharing. It really doesn't surprise me

          Andrew

          Show
          Andrew Nicols added a comment - Stephen McFarlane the issue you're describing is unrelated to this one - Jerome raised a similar issue in MDL-41328 Colin Chambers Thanks for sharing. It really doesn't surprise me Andrew
          Hide
          Ralf Krause added a comment -

          Hi Stephan,
          there is no iOS 6.3 ... I think that you will use iOS 6.1.3
          Ralf

          Show
          Ralf Krause added a comment - Hi Stephan, there is no iOS 6.3 ... I think that you will use iOS 6.1.3 Ralf
          Hide
          Jérôme Mouneyrac added a comment -

          Andrew, I think we can send it for integration?

          Show
          Jérôme Mouneyrac added a comment - Andrew, I think we can send it for integration?
          Hide
          Aparup Banerjee added a comment -

          fyi, this works! (tested @ mdlsite-2431)

          Show
          Aparup Banerjee added a comment - fyi, this works! (tested @ mdlsite-2431)
          Hide
          Andrew Nicols added a comment -

          Thanks to all of those who have helped test this over the past week. I think that it solves the issue we've been seeing. The fact that TinyMCE have implemented essentailly same patch for 4.X gives me greater confidence still.

          Show
          Andrew Nicols added a comment - Thanks to all of those who have helped test this over the past week. I think that it solves the issue we've been seeing. The fact that TinyMCE have implemented essentailly same patch for 4.X gives me greater confidence still.
          Hide
          Damyon Wiese added a comment -

          Thanks Andrew - it's great to get this working. The solution seems so small in the end.

          I added a bit to the testing instructions to test for regressions on non-safari ios browsers.

          Integrated this to master, 25 and 24 only as it's not a security bug.

          Show
          Damyon Wiese added a comment - Thanks Andrew - it's great to get this working. The solution seems so small in the end. I added a bit to the testing instructions to test for regressions on non-safari ios browsers. Integrated this to master, 25 and 24 only as it's not a security bug.
          Hide
          Damyon Wiese added a comment -

          Ankit said he could not reproduce this bug before the patch. I tested and could reproduce it on the stable weekly from the 8th, and could not reproduce it on the stable weekly on the 15th.

          Looking...

          Show
          Damyon Wiese added a comment - Ankit said he could not reproduce this bug before the patch. I tested and could reproduce it on the stable weekly from the 8th, and could not reproduce it on the stable weekly on the 15th. Looking...
          Hide
          Damyon Wiese added a comment -

          Git bisect says this was fixed by:

          bf7c86cfcf4612477e9ee417f6ad2fbc52c48cc4

          Which was part of MDL-39851 (Full screen popups on small devices).

          Show
          Damyon Wiese added a comment - Git bisect says this was fixed by: bf7c86cfcf4612477e9ee417f6ad2fbc52c48cc4 Which was part of MDL-39851 (Full screen popups on small devices).
          Hide
          Damyon Wiese added a comment -

          So the filepicker changes fix this in some places (by moving to M.core.dialogue and changing the DD code there a bit). More testing - and turning editing on brings back the bug - will check that on last weekly and then current integration now.

          Show
          Damyon Wiese added a comment - So the filepicker changes fix this in some places (by moving to M.core.dialogue and changing the DD code there a bit). More testing - and turning editing on brings back the bug - will check that on last weekly and then current integration now.
          Hide
          Damyon Wiese added a comment -

          So testing on 2.5 - before this patch I could reproduce by editing the course settings with editing turned either on or off. After this patch, you can still type - but you can't move the cursor: (MDL-41328).

          Testing on 2.6 - before bf7c86cfcf4612477e9ee417f6ad2fbc52c48cc4 I could reproduce by editing the course settings with editing turned either on or off. After bf7c86cfcf4612477e9ee417f6ad2fbc52c48cc4 I could reproduce only editing the course settings with editing turned on. With this patch and editing turned on, editing the course page I could still type, but I couldn't move the cursor (MDL-41328).

          Show
          Damyon Wiese added a comment - So testing on 2.5 - before this patch I could reproduce by editing the course settings with editing turned either on or off. After this patch, you can still type - but you can't move the cursor: ( MDL-41328 ). Testing on 2.6 - before bf7c86cfcf4612477e9ee417f6ad2fbc52c48cc4 I could reproduce by editing the course settings with editing turned either on or off. After bf7c86cfcf4612477e9ee417f6ad2fbc52c48cc4 I could reproduce only editing the course settings with editing turned on. With this patch and editing turned on, editing the course page I could still type, but I couldn't move the cursor ( MDL-41328 ).
          Hide
          Andrew Nicols added a comment -

          Damyon Wiese that makes some sense - AIR, MDL-41328 changed the dialogues to not plug Y.Plugin.Drag to the dialogues if the dialogue should be responsive, and the screen is too small.

          This issue with iframemd contenteditable + iOS is only exhibitted when you have any touch handlers present on the page.

          I would argue that this patch should still land as there could be TinyMCE editors on pages where drag/drop is still present in other forms. For example, if you have editing turned on, we have block drag/drop enabled, and this will once again break any iOS editors.

          Show
          Andrew Nicols added a comment - Damyon Wiese that makes some sense - AIR, MDL-41328 changed the dialogues to not plug Y.Plugin.Drag to the dialogues if the dialogue should be responsive, and the screen is too small. This issue with iframemd contenteditable + iOS is only exhibitted when you have any touch handlers present on the page. I would argue that this patch should still land as there could be TinyMCE editors on pages where drag/drop is still present in other forms. For example, if you have editing turned on, we have block drag/drop enabled, and this will once again break any iOS editors.
          Hide
          Ankit Agarwal added a comment -

          Thanks Damyon, for all the investigation and testing.

          Testing on the left out 24 branch.

          Show
          Ankit Agarwal added a comment - Thanks Damyon, for all the investigation and testing. Testing on the left out 24 branch.
          Hide
          Andrew Nicols added a comment -

          Confirmed - block moving being present on the screen causes this to break once more on master.
          I've modified the testing instructions to suggest turning editing on on the course.

          This can affect students too - editing user profile pages for example when they have editing turned on their My Moodle will probably cause this (though I'm not 100% sure). Any third-party plugin which gives users the ability to move things on the screen (e.g. a local plugin which adds on-screen notes and reminders - Mark Ward has been developing such a system).

          Show
          Andrew Nicols added a comment - Confirmed - block moving being present on the screen causes this to break once more on master. I've modified the testing instructions to suggest turning editing on on the course. This can affect students too - editing user profile pages for example when they have editing turned on their My Moodle will probably cause this (though I'm not 100% sure). Any third-party plugin which gives users the ability to move things on the screen (e.g. a local plugin which adds on-screen notes and reminders - Mark Ward has been developing such a system).
          Hide
          Ankit Agarwal added a comment -

          On 24 the issue I was able to type after refocusing. I noticed MDL-41328 while testing it.

          Passing.
          Thanks

          Show
          Ankit Agarwal added a comment - On 24 the issue I was able to type after refocusing. I noticed MDL-41328 while testing it. Passing. Thanks
          Hide
          Damyon Wiese added a comment -

          There was a young man named McGee
          Who thought squashing bugs was easy
          He tried it one day
          And to his dismay
          The bug guts made his keyboard all greasy

          Thanks!

          This has issue has been fixed and released in Moodle.

          Show
          Damyon Wiese added a comment - There was a young man named McGee Who thought squashing bugs was easy He tried it one day And to his dismay The bug guts made his keyboard all greasy Thanks! This has issue has been fixed and released in Moodle.
          Hide
          Luke Bryan added a comment -

          Could someone please provide a link to the patch of the final fix for this issue? I'm seeing what I believe is a similar issue, in another tinymce project. Is there a certain version of Tinymce that includes the fix?

          Show
          Luke Bryan added a comment - Could someone please provide a link to the patch of the final fix for this issue? I'm seeing what I believe is a similar issue, in another tinymce project. Is there a certain version of Tinymce that includes the fix?
          Hide
          Andrew Nicols added a comment -

          Hi Luke Bryan,

          The commit in Moodle master can be found at https://github.com/moodle/moodle/commit/be94c6d88d7262e2d80e63c252382eb533c3835a
          This has also been fixed upstream in TinyMCE 4.X in a slightly different way at https://github.com/tinymce/tinymce/commit/19946dbbad203788b79395da6c3fb645022214a4

          We don't generally modify upstream sources, and are using TinyMCE 3.X, so our fix is more appropriate in this case.

          I should also point you at the fix I've put forward in MDL-41328 - https://github.com/andrewnicols/moodle/compare/MDL-41328-m.

          Andrew

          Show
          Andrew Nicols added a comment - Hi Luke Bryan , The commit in Moodle master can be found at https://github.com/moodle/moodle/commit/be94c6d88d7262e2d80e63c252382eb533c3835a This has also been fixed upstream in TinyMCE 4.X in a slightly different way at https://github.com/tinymce/tinymce/commit/19946dbbad203788b79395da6c3fb645022214a4 We don't generally modify upstream sources, and are using TinyMCE 3.X, so our fix is more appropriate in this case. I should also point you at the fix I've put forward in MDL-41328 - https://github.com/andrewnicols/moodle/compare/MDL-41328-m . Andrew
          Hide
          Ralf Krause added a comment - - edited

          Hi Andrew,

          I tested your code for TinyMCE in Moodle on your page http://sandpit.andrewrn.co.uk/36803/mod/forum/view.php?id=2. This page works fine on the iPad with Safari, Chrome, Coast (Opera), and MoodlEZ. Do you use a private code implementation of TinyMCE on your test site??

          I installed the newest Moodle 2.5.2+ (20130927) and 2.6dev (20130927) on my own server and I found that the TinyMCE does not show the editor symbols with MoodlEZ on the iPad. Is there a browser identification in the Moodle code which does not work with MoodlEZ?

          Best regards, Ralf

          Show
          Ralf Krause added a comment - - edited Hi Andrew, I tested your code for TinyMCE in Moodle on your page http://sandpit.andrewrn.co.uk/36803/mod/forum/view.php?id=2 . This page works fine on the iPad with Safari, Chrome, Coast (Opera), and MoodlEZ. Do you use a private code implementation of TinyMCE on your test site?? I installed the newest Moodle 2.5.2+ (20130927) and 2.6dev (20130927) on my own server and I found that the TinyMCE does not show the editor symbols with MoodlEZ on the iPad. Is there a browser identification in the Moodle code which does not work with MoodlEZ? Best regards, Ralf
          Hide
          Andrew Nicols added a comment -

          Hi Ralf,

          The version on my test site is nothing special - it's the same TinyMCE implementation.

          Are you able to test MoodlEZ against qa.moodle.net? This is running the latest daily release.

          If it's still not working, could you raise an issue. If it is, then you could try clearing your browser cache, and purging Moodle caches.

          Cheers,

          Andrew

          Show
          Andrew Nicols added a comment - Hi Ralf, The version on my test site is nothing special - it's the same TinyMCE implementation. Are you able to test MoodlEZ against qa.moodle.net? This is running the latest daily release. If it's still not working, could you raise an issue. If it is, then you could try clearing your browser cache, and purging Moodle caches. Cheers, Andrew
          Hide
          Ralf Krause added a comment -

          moodlEZ shows the gray editor symbols on qa.moodle.net.

          Show
          Ralf Krause added a comment - moodlEZ shows the gray editor symbols on qa.moodle.net.
          Hide
          Ralf Krause added a comment -

          With Moodle 2.6dev (20130927) the coloured editor symbols are shown in the moodlEZ app after deleting the Moodle cache and after a few reloads of the page.

          Show
          Ralf Krause added a comment - With Moodle 2.6dev (20130927) the coloured editor symbols are shown in the moodlEZ app after deleting the Moodle cache and after a few reloads of the page.
          Hide
          Ralf Krause added a comment -

          In Moodle 2.5.2 (20130909) i do not get any symbol with the moodlEZ app. I also deleted the Moodle cache and I tried to reload the page a few times.

          Show
          Ralf Krause added a comment - In Moodle 2.5.2 (20130909) i do not get any symbol with the moodlEZ app. I also deleted the Moodle cache and I tried to reload the page a few times.
          Hide
          Ralf Krause added a comment - - edited

          Hi Andrew, the developer of MoodlEZ wrote the following statement:

          Hi, this seems to be a moodle+tinymce editor problem. We just use a regular UIWebView and send UIWebView user agent value postfixed with "(moodlEZ)" string. Cheers
          Show
          Ralf Krause added a comment - - edited Hi Andrew, the developer of MoodlEZ wrote the following statement: Hi, this seems to be a moodle+tinymce editor problem. We just use a regular UIWebView and send UIWebView user agent value postfixed with "(moodlEZ)" string. Cheers
          Hide
          Ralf Krause added a comment - - edited

          Yes, the browser identification seems to be very normal ... I got the following strings from the webserver protocol

          "Mozilla/5.0 (iPad; CPU OS 6_1_3 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Mobile/10B329 (moodlEZ)"
          "Mozilla/5.0 (iPad; CPU OS 7_0_2 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) Mobile/11A501 (moodlEZ)"

          I asked for possible timeouts of javascript execution. It could also be an authentication issue, may be tinymce editor js scripts are under a protected path?

          Show
          Ralf Krause added a comment - - edited Yes, the browser identification seems to be very normal ... I got the following strings from the webserver protocol "Mozilla/5.0 (iPad; CPU OS 6_1_3 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Mobile/10B329 (moodlEZ)" "Mozilla/5.0 (iPad; CPU OS 7_0_2 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) Mobile/11A501 (moodlEZ)" I asked for possible timeouts of javascript execution. It could also be an authentication issue, may be tinymce editor js scripts are under a protected path?
          Hide
          Andrew Nicols added a comment -

          Hi Ralf,

          Since this is working as expected under all other iOS browsers excepting MoodlEZ, that would really suggest an issue with MoodlEZ rather than Moodle. I would suggest creating an issue with it's authors and/or creating a new issue on the Moodle tracker. The issue you're describing doesn't seem to bear much resemblance to this issue or any others that I'm aware of. This issue concerns a specific problem with iOS Safari relating to keyboard input following touch events inside an iframe. It's a bug in Safari which we've successfully worked around in TinyMCE and Moodle.

          Best wishes,

          Andrew

          Show
          Andrew Nicols added a comment - Hi Ralf, Since this is working as expected under all other iOS browsers excepting MoodlEZ, that would really suggest an issue with MoodlEZ rather than Moodle. I would suggest creating an issue with it's authors and/or creating a new issue on the Moodle tracker. The issue you're describing doesn't seem to bear much resemblance to this issue or any others that I'm aware of. This issue concerns a specific problem with iOS Safari relating to keyboard input following touch events inside an iframe. It's a bug in Safari which we've successfully worked around in TinyMCE and Moodle. Best wishes, Andrew

            People

            • Votes:
              9 Vote for this issue
              Watchers:
              20 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile