Spell check not working IE11

4 posts, 0 answers
  1. Ned
    Ned avatar
    6 posts
    Member since:
    Dec 2011

    Posted 21 Jul 2014 Link to this post

    It's possible this should go under the RadSpell control, but...

    In IE11, if the next wrong word doesn't have any suggestions, the spell check doesn't open the commands window (the one with Ignore/Ignore All/Change Manually/etc), and the spell check can't continue.  This happens in both iframe and div modes.  No errors are thrown.

    Also, in IE11, when the RadEditor is set to ContentAreaMode="Div" and contained inside an iframe, clicking on the spell check commands window for the first misspelled word results in the following JavaScript error:

    Object doesn't support property or method 'createTextRange'.

    Screenshot attached.
  2. Ianko
    Ianko avatar
    1507 posts

    Posted 23 Jul 2014 Link to this post

    Hello Ned,

    The described issues are bugs and I logged them into our database for fixing.

    As per to the reported issues you can follow these feedback portal items for further updates and workarounds on the matters:

    As reward and appreciation for reporting these issues, I am updating your Telerik points.

    For the time being you can resolve them both by adding a meta tag to force the IE10 compatibility mode of the IE browser:

    <meta http-equiv="X-UA-Compatible" content="IE=10" />



    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.

  3. DevCraft R3 2016 release webinar banner
    RAJEEV avatar
    3 posts
    Member since:
    Jun 2013

    Posted 30 Apr 2015 Link to this post

    Was this issue fixed in any of the current releases. We are encountering this issue after migrating to IE11. Putting in the <meta http-equiv="X-UA-Compatible" content="IE=10" /> tag is not helping. We still get the same error.
  5. Ianko
    Ianko avatar
    1507 posts

    Posted 04 May 2015 Link to this post


    Both issues have been resolved with the release of the Q1 2015 version.


    See What's Next in App Development. Register for TelerikNEXT.

Back to Top