When Highlighting text and choosing some formatting options the highlight disappears completely, though the text is still chosen.
Steps to Reproduce
1) Add some text to WYSIWYG
2) Highlight text
3) Choose dropdown options for - Font or Size
As actual result text is no longer visually highlighted (please see attached video as zip file - that's actually tar, I just renamed it as zip and split on two parts)
But in demo on the your site Text remains highlighted (http://demos.telerik.com/kendo-ui/editor/index). Any ideas how to fix it?
5 Answers, 1 is accepted
It appears that you are using our built-in Bootstrap theme, but it has been modified, for example the dropdown items hover color is light blue and not gray (default). So here's a dojo example, in which the Editor uses the Bootstrap theme and there are no custom CSS rules added. The highlighted text remains highlighted when the dropdowns are expanded. Could you modify the linked example by adding your custom CSS, in order for the problematic behavior to be reproduced, and link it back for further review?
Based on your dojo example I tried to figure out the reason of this odd behavior. I suspected it depends on which container for wyswig editor you use.
<textarea id="editor" rows="10" cols="30" style="width:100%;height:400px">
<!-- could be div or span -->
If it's <textarea> then highlighting works fine, but if it's <div>/<span> then highlighting does not work (I believe it depends actually do we have iframe inside or not). Any thoughts on that?
Thank you for the additional information provided. We logged this behavior for fixing. Here's the corresponding Github issue, through which the bug's status can be tracked.
I updated your Telerik points for reporting this issue.
Any progress on this issue? Can we expect hotfix or at least understand which new version of Kendo Editor will get the fix?
Unfortunately the bug in question hasn't been scheduled for fixing yet, which prevents us from providing an estimate which particular release a fix will be included in. Fixes for issues with higher priority or severity are planned to be released for R1 2018, so at this point releasing a fix to this bug in R1 2018 seems unlikely.