Our team is fixing all WCAG guideline bugs in our product. The 3.1.1 guideline can't be met because the Kendo editor doesn't allow for setting a lang attribute on the iframe document, nor does the editor infer the language from the parent document and add that lang attribute.
Open the editor example page (https://demos.telerik.com/kendo-ui/editor/index). Note that the editor iframe document contains <html> at the top but does not contain a lang="en" attribute within it. Further, edit the example on the page and add lang="en" to the <html> attribute at the top of the example. Run the example. The iframe still does not contain the lang="en" attribute.
Include the lang attribute on the child document when the parent document contains one or make a setting available in the configuration JSON for the editor to include a lang attribute in the child document when an iframe is used.
Using the MobileView AngularJS directive throws an error upon initialization. This is a regression from 2019 R2 release.
1 - when use bootstrap v4 theme, ddl does not handle long names gracefully, please find in attachment example in bootstrap v4 & silver themes, also here are the dojo exaples
2 - for grid and separate controls validation message has diff view
should be the same
we set same data for all 3 pickers, 1 & 3 open immediately as soon as we set the date & than clear them, 2 first clear than open, in the end all cleared but some still show any date but current
what we want:
if we set the date & than cleared DP, DP should show current date despite was it opened or not
I am currently experiencing an issue between the Kendo ContextMenu and the Kendo EditorFor. When I open the ContextMenu inside of the EditorFor it display offset relative to the cursor, both the left and top values are completely incorrect relative to the editor.
Attached you will find a solution where this issue has been replicated, I removed the scripts folder in order to keep the file size small. I hope this can be fixed soon.
I'd like to ask for a demo which utilizes the most up to date approach to creating a Kendo UI Grid using NPM, TypeScript, and in a SharePoint 2019 with a Gulp serve environment.
Thank you for your consideration!
We recently raised a ticket: 1424874.
We would like to request this ability to be added as a feature.
An error is thrown in the browser's console when pasting text + image from Word into the Kendo UI Editor: "Not allowed to load local resource: file:///C:/Users/..."
This is due to the inability of the browser to access the image file, located on the client machine.
The explanation of the above is the following. If you test the following sample (note, that it does not use Kendo) in Chrome, and try to paste text + image in the contenteditable <div>, you will observe the same error. The Editor also renders its content in an editable div element. The browser does not recognize that the user attempts to paste an image. Instead of reading the image data and loading it as a base64 string to the src attribute of the <img> element it generates an <img> tag which points to the clipboard location of the file on the client machine. As the browser is not allowed to access such resource, it trows the error observed and the image is not rendered.
To resolve this issue, when pasting only an image (no text), the Editor has its own internal implementation. Therefore, the user is able to paste images (e.g. clicking on the image in Word->Ctrl +C->then Ctrl + V in the Editor). However, when pasting it together with text, the widget does recognize the text and does not apply the custom processing aimed to convert the image. Therefore the native browser behavior of pasting images is exhibited.
I am working extensively with Kendo UI Drawing API, specifically with drawDOM and exportPDF methods. I encountered a strange issue, which leads to the generation of corrupt PDF files.
After several attempts to analyze the problem, I found a small piece of code that allows to systematically reproduce the issue. You can find the code as attached.
Opening the example page with Chrome browser I got a corrupted PDF file, while Internet Explorer seems to generate a valid PDF file starting from the same source page.
Checking with an online PDF validator, the file generated by Chrome exploits this validation error:
“The content stream contains an invalid operator.
The operator has an invalid number of operands.”
I’m not skilled with PDF internals, but comparing the valid file of IE and the invalid file of Chrome, I noticed that an “infinite” value appears in the invalid PDF.
The row in the valid PDF is “1 0 0 -1 -9494.7900391 -9965.5996094 cm“, while the same row in the invalid PDF is “1 0 0 -1 Infinity Infinity cm”.
I noticed that the presence of an “Infinite” value is the common behavior whenever the corrupt PDF problem occurs.
1. Open column menu
2. Using arrow keys, go to Filter menu item.
3. Hit right arrow to open Filter submenu
4. Tab through filter submenu
5. Hit escape.
Expected behaviour: Filter submenu closes and focus returns to the parent column menu
Actual behaviour: Both filter and column menu are closed.
This is an issue for accessibility users - there doesn't seem to be a way to return to the parent filter menu using the keyboard without closing all menus and reopening them.
There is one way for it to occur, and that is to use the mouse to place the focus on the Filter menu background - in this case hitting escape will close the Filter menu and focus will be returned to the parent column menu. However this is impractical for an accessibility user who is relying solely on keyboard navigation.
An example of where this (mostly) works is on the Columns submenu - the user can use the left arrow key or Escape to close the child menu or alternatively keep tabbing and they will eventually return to the parent menu (though if they do tab within the child menu, hitting Escape will close both the child and parent menus).
video to understand the exact behaviour
In cases when we have loadOnDemand set to true and we want to populate the value of the DropDownTree initially we need a way to check if this value is part of the available options. One possible solution is adding a valueMapper function similar to the one use in virtualization scenarios.
Regression introduced in version 2019.2.514.
The MobileView title is not rendered.
The title is rendered.
The out of the box legend does not offer the ability to split its items and to show them as labels over the series (graphs).
Extract my attached zip file and look at the MSWord document which shows you where I would like to position the 2 legends.
Currently events >24h are automatically shown in the all day area. This is confusing if the event starts or ends somewhere during the day. E.g. it starts at 5 p.m. on tuesday and ends on 11 a.m. on thursday. Noone knows when the resource is really available if the event is shown as all day from tuesday to thursday. There should be an option to turn that behaviour off and show such events as regular events. Maybe the only thing needing change is this line in _renderEvents: var isMultiDayEvent = event.isAllDay || event.end.getTime() - event.start.getTime() >= MS_PER_DAY;