When assigning multiple resources and percentages, the first item in list always goes back to 100%.
It saves back to UI correctly but as soon as you leave or refresh page it goes back to 100% on first item and that's what's saved in database.
The online demo has the same code but demo doesn't save at all to test.
See attached screen shots.
Bug report
It is not possible to print a PDF through the PDFViewer print tool on Desktop Chrome and Android Chrome.
Reproduction of the problem
Load PDFViewer Basic Usage demo and tap on Print tool - https://demos.telerik.com/aspnet-ajax/pdfviewer/overview/defaultcs.aspx
Current behavior
Android - "There was a problem printing the page. Please try again." - no preview
Windows - the Print dialog shows and closes automatically
Expected/desired behavior
Print preview is available, allowing you to find a printer and print
Hi Telerik,
Just a heads-up - some of the demo pages are generating errors:
I have found this on:
The issue can be replicated with AutoCompleteBox demo: https://demos.telerik.com/aspnet-ajax/autocompletebox/examples/default/defaultcs.aspx
Set the SingleLineEntries property to "Enabled", and add a new Entry to the AutoCompleteBox. At this point, the page will scroll up and as a result hiding the AutoCompleteBox.
I just installed the latest release (Telerik_UI_for_ASP.NET_AJAX_2023_1_314) and the program gives me an error.
This is the error :
Test Environment:
OS: Windows_11URL: https://demos.telerik.com/aspnet-ajax/calendar/overview/defaultcs.aspx
Tool: Accessibility Insight for web.
Repro Steps:
1. Open URL: https://demos.telerik.com/aspnet-ajax/calendar/overview/defaultcs.aspx page in Edge Browser.
2. Navigate to calendar under overview Section by using tab key.
3. Run Accessibility Insight tool.
4. Verify the bug.
Actual Behavior:
Ensures the contrast foreground and background colors doesn't meet WCAG 2AA contrast ratio thresholds.
Expected Behavior:
Ensures the contrast between foreground and background colors meets WCAG 2 AA contrast ratio thresholds.
Environment (OS, Application, Versions)
Screen Reader: NVDA 2022.1
Repro-Steps:
Deleting of a table by delete or backspace key does not work when the selection contains only the table. Steps to reproduce: 1. Set the following content <p>test p1</p> <table> <tbody> <tr> <td>test</td> <td>test</td> </tr> </tbody> </table> <p>test p2</p> 2. Select the table only and press delete or backspace key Actual: Only the content has been deleted. Expected: The table and its content to be deleted. Workaround: <telerik:RadEditor ID="RadEditor1" runat="server"> </telerik:RadEditor> <script type="text/javascript"> (function () { var $T = Telerik.Web.UI; var utils = $T.Editor.Utils; var isTableSelected = function (selected) { if (utils.isTag(selected, "table")) { return true; } var table = utils.getElementParentByTag(selected, "TABLE"); return table && !!utils.getElementParentByCondition(selected, function (current) { return utils.isAncestorOrSelf(table, current) && utils.isSingleChild(current); }); }; // Fix for delete table by delete or backspace key var formatFragments = $T.Editor.DeleteSelectionCommand.prototype.formatFragments; $T.Editor.DeleteSelectionCommand.prototype.formatFragments = function (fragments) { var cmd = this; var selected = cmd.get_editor().getSelectedElement(); if (isTableSelected(selected) && fragments.length) { var table = utils.isTag(selected, "table") ? selected : utils.getElementParentByTag(selected, "TABLE"); var $table = $telerik.$(table); var data = $table.find("th,td"); var firstCell = data.first().get(0); var lastCell = data.last().get(0); var firstFragment = fragments[0]; var lastFragment = fragments[fragments.length - 1]; var firstSelected = firstFragment.nodes[0]; var lastSelected = lastFragment.nodes[lastFragment.nodes.length - 1]; if ((firstSelected == firstCell || firstSelected == firstCell.firstChild || cmd.isMarker(firstCell.firstChild)) && (lastSelected == lastCell || lastSelected == lastCell.lastChild)) { $table.find("." + cmd.getMarkersCssClass()).insertBefore(table); $telerik.$(table).remove(); return; } } formatFragments.call(cmd, fragments); }; // Fix for select and delete a table by the DomInspector in Chrome var Modules = $T.Editor.Modules; if (Modules && Modules.RadEditorDomInspector) { var removeSelectedElement = Modules.RadEditorDomInspector.prototype.removeSelectedElement; Modules.RadEditorDomInspector.prototype.removeSelectedElement = function (element) { if (isTableSelected(element)) { element = utils.isTag(element, "table") ? element : utils.getElementParentByTag(element, "TABLE"); } removeSelectedElement.call(this, element); }; } })(); </script>
at $IE.Print.dispose (<anonymous>:90:18)
Workaround:
Enable the external dialogs of the Editor/ImageEditor and modify dispose() function of the Print.ascx dialog:
Print.ascx
dispose: function ()
{
this._attachHandlers(false);
this._printBtn.dispose();
this._cancelBtn.dispose();
$IE.Print.callBaseMethod(this, "dispose");
},
In Chrome and IE the clicking of the SELECT button for the uploads is kinda difficult when using MATERIAL skin. See the following video: https://www.screencast.com/t/VBe1zSss7c How-to fix the bug: 1. Create a CSS file named dialog.css 2. Put the following class in the dialog.css file: .RadUpload .ruFileInput { height: 50px !important; } 3. Set the DialogsCssFile property to point to the dialog.css file: <telerik:RadEditor ID="RadEditor1" Skin="Material" RenderMode="Lightweight" DialogsCssFile="~/dialog.css" runat="server"> <ImageManager ViewPaths="~/Images" UploadPaths="~/Images" /> </telerik:RadEditor> 4. Save the page. 5. Clear the browser cache and load the page in it. If needed reload the dialog contents 3-4 times to clear the cache -> right click and choose Reload frame from the Chrome context menu.
Elapsed time, Estimated time and Speed are not calculated correctly.
This issue causes some content added by user to be not included when Track Changes are accepted. This is because the text is inserted in the INS tag, which is determined as deleted text by the feature's logic.
This issue causes incorrect user experience. The users are forced to do multiple actions to replace a word while using the Track Changes feature.
All dialog windows triggered from SmartTags (ODataDataSource configuration wizard per say) are distorted and mostly or completely unusable in HDPI environments (150% scaling). In particular we can observe few main points: * Window too big to fit on the screen * Text too big to fit in designated area * Layout completely distorted * Icons not showing correctly
The problem is when not tracked content does not exist. User cannot set the cursor outside the tracked content. Although, typing should split the tracked text and user should be able to type in not tracked text when the feature is disabled.