The problem can be seen on the Telerik demo editor. I'm using safari on iOS 7.1. I'll attach screenshots to show the problem.
Steps to reproduce:
Tap in the editor, placing the cursor somewhere in the middle of the editable area. (screenshot 1)
Start hitting Return on the iOS keyboard until the cursor reaches the bottom of the editable area. (screenshot 2)
At this point, if you continue to hit Return, rather than staying at the bottom of the editable area and scrolling the editor content up, the cursor continues moving down past the bottom of the editor. In screenshot3 you can see the cursor well below the editor at the bottom of the screen.
Is there a workaround solution for this problem? Can we expect the problem to fixed in a future build?
Steps to reproduce:
Tap in the editor, placing the cursor somewhere in the middle of the editable area. (screenshot 1)
Start hitting Return on the iOS keyboard until the cursor reaches the bottom of the editable area. (screenshot 2)
At this point, if you continue to hit Return, rather than staying at the bottom of the editable area and scrolling the editor content up, the cursor continues moving down past the bottom of the editor. In screenshot3 you can see the cursor well below the editor at the bottom of the screen.
Is there a workaround solution for this problem? Can we expect the problem to fixed in a future build?
9 Answers, 1 is accepted
0
Hi Trevor,
We are aware of this issue under IOS. Unfortunately, I am not able to give you time estimation when it will be fixed. The issue is reproduced only with iframe, so you could resolve the issue by setting ContentAreaMode property to Div if it's applicable in your scenario.
Thank you for your patience.
Regards,
Joana
Telerik
We are aware of this issue under IOS. Unfortunately, I am not able to give you time estimation when it will be fixed. The issue is reproduced only with iframe, so you could resolve the issue by setting ContentAreaMode property to Div if it's applicable in your scenario.
Thank you for your patience.
Regards,
Joana
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0

Trevor
Top achievements
Rank 1
answered on 02 May 2014, 07:09 PM
Hi Joana,
Unfortunately there is an even more troublesome bug with contentareamode=div on iOS. This can also been seen on the Telerik (div) demo editor:
https://demos.telerik.com/aspnet-ajax/editor/examples/contentareamodediv/defaultvb.aspx
Using iOS, tap somewhere in the middle of the page so there is content above the cursor. Now click the 'Insert Table' toolbar button to insert a table. Notice that the table is added ABOVE all the content, not at the cursor position.
Can you offer a solution to this problem?
Thanks,
Trevor.
Unfortunately there is an even more troublesome bug with contentareamode=div on iOS. This can also been seen on the Telerik (div) demo editor:
https://demos.telerik.com/aspnet-ajax/editor/examples/contentareamodediv/defaultvb.aspx
Using iOS, tap somewhere in the middle of the page so there is content above the cursor. Now click the 'Insert Table' toolbar button to insert a table. Notice that the table is added ABOVE all the content, not at the cursor position.
Can you offer a solution to this problem?
Thanks,
Trevor.
0

Trevor
Top achievements
Rank 1
answered on 05 May 2014, 08:53 PM
Can I get an update on this issue?
0
Hi Trevor,
Indeed, there is an issue with the insertion of a table. I will escalate the issues to our developers and we will fix them as soon as possible. In the meantime, you could use the following workaround but there are some scenarios that are not handled:
​
Thank you for your patience. I have updated your telerik points for your reports.
Regards,
Joana
Telerik
Indeed, there is an issue with the insertion of a table. I will escalate the issues to our developers and we will fix them as soon as possible. In the meantime, you could use the following workaround but there are some scenarios that are not handled:
<
telerik:RadEditor
ID
=
"RadEditor1"
runat
=
"server"
ContentAreaMode
=
"Div"
OnClientLoad
=
"OnClientLoad"
OnClientCommandExecuting
=
"OnClientCommandExecuting"
></
telerik:RadEditor
>
​
<script type=
"text/javascript"
>
var
cursorPosition =
null
;
var
editor;
function
OnClientLoad(sender, args) {
editor = sender;
editor.add_selectionChange(getCursorPosition);
}
function
getCursorPosition() {
cursorPosition = editor.getSelection().getRange();
}
function
OnClientCommandExecuting(sender, args) {
var
commandName = args.get_commandName();
if
(commandName ==
"InsertTable"
|| commandName ==
"TableWizard"
) {
sender.getSelection().selectRange(cursorPosition);
}
}
</script>
Thank you for your patience. I have updated your telerik points for your reports.
Regards,
Joana
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0

Trevor
Top achievements
Rank 1
answered on 08 May 2014, 02:40 PM
5 days later, still waiting for an update on this issue.
Can I get an update please?
Can I get an update please?
0

Trevor
Top achievements
Rank 1
answered on 09 May 2014, 01:47 PM
Hi Joana,
I already implemented a similar solution, however, it does not solve the problem due ANOTHER bug I also reported: OnClientSelectionChange only fires the first time you tap in the content area. Subsequent taps do not cause OnClientSelectionChange to fire.
This means the table will always be inserted at the FIRST TAP LOCATION. If the user taps into the content area, then taps elsewhere in the content area, then inserts a table, the table will be added at the initial tap location - not the current cursor position.
Can you provide a solution to this problem?
Thanks,
Trevor.
I already implemented a similar solution, however, it does not solve the problem due ANOTHER bug I also reported: OnClientSelectionChange only fires the first time you tap in the content area. Subsequent taps do not cause OnClientSelectionChange to fire.
This means the table will always be inserted at the FIRST TAP LOCATION. If the user taps into the content area, then taps elsewhere in the content area, then inserts a table, the table will be added at the initial tap location - not the current cursor position.
Can you provide a solution to this problem?
Thanks,
Trevor.
0
Hello Trevor,
The last mentioned problem is discussed in the other forum thread, opened by you. And as mentioned there, this is a browser behavior due to which our control events are failing.
When it comes to RadEditor control, you should be aware that it is used with native editable HTML elements. In most browsers there are events and functionalities further implemented about these elements, which cause our control to break in some scenarios.
Also finding fixes and workarounds related to touch devices is a complex matter which is a time-consuming action and our policy is to log tasks for further investigation. These tasks are thoroughly investigated and planned for implementation by the dev team. Due to the complexity of these matters after a possible completion of the task, the QAs start testing the implemented fix functionality. After competing this procedure successfully, the implemented fix is getting placed into an official release, with which you could upgrade the used suite and take advantage of the implemented resolutions.
I can suggest following the release notes of future releases for major RadEditor improvements about touch devices.
Regards,
Ianko
Telerik
The last mentioned problem is discussed in the other forum thread, opened by you. And as mentioned there, this is a browser behavior due to which our control events are failing.
When it comes to RadEditor control, you should be aware that it is used with native editable HTML elements. In most browsers there are events and functionalities further implemented about these elements, which cause our control to break in some scenarios.
Also finding fixes and workarounds related to touch devices is a complex matter which is a time-consuming action and our policy is to log tasks for further investigation. These tasks are thoroughly investigated and planned for implementation by the dev team. Due to the complexity of these matters after a possible completion of the task, the QAs start testing the implemented fix functionality. After competing this procedure successfully, the implemented fix is getting placed into an official release, with which you could upgrade the used suite and take advantage of the implemented resolutions.
I can suggest following the release notes of future releases for major RadEditor improvements about touch devices.
Regards,
Ianko
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0

Trevor
Top achievements
Rank 1
answered on 14 May 2014, 05:21 PM
Hi,
The problem may be a result of browser behavior, however, it is still a bug in your editor. Please re-read the description of the problem:
"This means the table will always be inserted at the FIRST TAP LOCATION. If the user taps into the content area, then taps elsewhere in the content area, then inserts a table, the table will be added at the initial tap location - not the current cursor position."
This is a MAJOR bug in the Editor; the root cause of the bug is completely irrelevant to *your* customers.
This needs to be resolved for us to move forward with the Telerik editor. Please let me know when I can expect to see this bug resolved or please provide a functional workaround.
Thank you,
Trevor.
The problem may be a result of browser behavior, however, it is still a bug in your editor. Please re-read the description of the problem:
"This means the table will always be inserted at the FIRST TAP LOCATION. If the user taps into the content area, then taps elsewhere in the content area, then inserts a table, the table will be added at the initial tap location - not the current cursor position."
This is a MAJOR bug in the Editor; the root cause of the bug is completely irrelevant to *your* customers.
This needs to be resolved for us to move forward with the Telerik editor. Please let me know when I can expect to see this bug resolved or please provide a functional workaround.
Thank you,
Trevor.
0
Hi Trevor,
I understand the frustration from this problem and I can confirm that such behavior and resulted issues due to browser native limitations will be properly handled in the Telerik controls.
As Joana mentioned the problem is logged as a bug report and the matter is brought to the attention of the dev team, although this matter is quite complex and possible and firm resolution cannot be found, tested and released for such short time frame.
Due to these matter I am unable to provide a firm information in which release this issues are going to be fixed.
Regards,
Ianko
Telerik
I understand the frustration from this problem and I can confirm that such behavior and resulted issues due to browser native limitations will be properly handled in the Telerik controls.
As Joana mentioned the problem is logged as a bug report and the matter is brought to the attention of the dev team, although this matter is quite complex and possible and firm resolution cannot be found, tested and released for such short time frame.
Due to these matter I am unable to provide a firm information in which release this issues are going to be fixed.
Regards,
Ianko
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.