Duplicated
Last Updated: 21 Jun 2022 23:03 by ADMIN
When the set_keepInScreenBounds method is called and you pass a true parameter, the popup of RadColorPicker is only partially visible (the tabs are hidden). 
Duplicated
Last Updated: 21 Jun 2022 22:38 by ADMIN
Created by: JP
Comments: 1
Category: Editor
Type: Bug Report
0

Steps to reproduce the text highlighting issue:

  1. Go to https://demos.telerik.com/aspnet-ajax/editor/examples/overview/defaultcs.aspx
  2. Delete the content and write a single line
  3. Use the mouse to highlight a portion of text starting at the end (right side) of the text and dragging toward the beginning (left side).
  4. Stop about halfway to the beginning of the text.
  5. Now, while the text is still highlighted, press shift and left arrow to continue selecting. This will work for some time until the highlight gets near the beginning, then, the highlight will start moving from the right side.
Duplicated
Last Updated: 14 Sep 2021 12:27 by ADMIN
According to the WAI-ARIA specification, the  Shift+Tab in Rich Text Box should focus the toolbar if the cursor is in the content area.As a side effect the Tab functionality get executed instead of Shift+Tab.

The behavior is correct in FF and IE, but not in Chrome

Possible workaround is overriding the InsertShiftTab command with this function:

<telerik:RadEditor runat="server" ID="RadEditor1">
</telerik:RadEditor>

<script type="text/javascript">
	Telerik.Web.UI.Editor.CommandList.InsertShiftTab = function (commandName, editor, oTool) {
		var oParent = editor.getSelectedElement();
		if (typeof (oParent.tagName) == "undefined")
			oParent = oParent.parentNode;

		var tdNode = Telerik.Web.UI.Editor.Utils.getElementParentByTag(oParent, "TD");
		if (tdNode) {
			Telerik.Web.UI.Editor.Utils.MoveToPreviousCell(tdNode, editor);
		}
		else {
			setTimeout(function () {
				var toolsArray = editor.get_toolAdapter().get_tools();
				var lastTool = toolsArray[toolsArray.length - 1].get_element();

				if (document.activeElement !== lastTool) {
					lastTool.focus();
				}
			}, 0);
		}
		return false;
	};
</script>
Duplicated
Last Updated: 14 Sep 2021 12:20 by ADMIN
A JavaScriptError is thrown when FileExplorer with enabled AsyncUplaod is used for multiple files uploading in IE. The message of the error is:
JavaScript runtime error: Object doesn't support property or method 'get_allowMultiRowSelection'

Steps to reproduce:
1. Open http://demos.telerik.com/aspnet-ajax/fileexplorer/examples/asyncupload/defaultcs.aspx in IE10
2. Open the FileExplorer's Upload dialog
3. Select 2 or more files for upload
4. Click the Upload button

Result: A JavaScript error is thrown.
Duplicated
Last Updated: 14 Sep 2021 11:57 by ADMIN
Create a page as below and assign a limited toolset to each editor in the code behind:


 <telerik:RadEditor  ID="RadEditor1" Skin="Default"  ContentAreaMode="Div"   runat="server"      Width="265px" Height="120px"  ToolsWidth="265px">
       <Content><p>A Word</p> </Content>
</telerik:RadEditor>
        
 <telerik:RadEditor  ID="RadEditor2" Skin="Default"  ContentAreaMode="Div"   runat="server"     Width="265px" Height="120px"  ToolsWidth="265px">
       <Content><p>A Word</p> </Content>
</telerik:RadEditor>
        
[Continue with this until ...]

 <telerik:RadEditor  ID="RadEditor10" Skin="Default"  ContentAreaMode="Div"   runat="server"     Width="265px" Height="120px"  ToolsWidth="265px">
       <Content><p>A Word</p> </Content>
</telerik:RadEditor>
        
Now display this page and right click for the top editor's Context Sensitive popup menu. Now scroll down to the bottom menu and right click for that menu's context sensitive menu. My experience is that this will erroneously produce the popup at the top of the browser. This is the most extreme example of a general behaviour where the vertical placement of popups is typically off the mark when working with multiple editors and ContentAreaMode="Div". Get rid of the ContentAreaMode="Div" and the problem disappears. 
Duplicated
Last Updated: 10 Aug 2021 09:59 by ADMIN
Because the TBODY THEAD and TFOOT elements are rendered in an incorrect order which is "header -> footer -> body" rather than "header -> body -> footer", the screen readers fail to present the data properly.
Duplicated
Last Updated: 01 Jun 2021 13:37 by ADMIN
ADMIN
Created by: Hristo Valyavicharski
Comments: 0
Category: DropDownList
Type: Bug Report
1