AcceptTrackChanges() - Server Side

3 posts, 0 answers
  1. tlp
    tlp avatar
    33 posts
    Member since:
    Oct 2006

    Posted 07 Mar Link to this post

    Hello,

    I am currently using version 2016.1.225.35 and I'm having issues with the server side AcceptTrackChanges() method. When the method is used it seems that formatting changes that have been made to the content (i.e., Bold) are not accepted. Other changes, like insert and delete, are accepted. I believe this use to work properly in the 2015 version. If we enable the command using the editor toolbar button (<telerik:EditorTool Name="AcceptAllTrackChanges" />), all changes are accepted (including the formatting changes).

    To reproduce this problem, include the editor in the page markup. Also, add a Button with the associated OnClick event. Within the code behind OnClick event, utilize the AcceptTrackChanges method to accept changes. Example is shown:

     

    protected void ButtonAcceptChanges_Click(object sender, EventArgs e)
    {
        RadEditorDesc.AcceptTrackChanges();               
    }

     

    Make changes within the editor content. Include formatting changes (i.e., bold) and then click on the Accept Changes button. You should notice that all changes are accepted other than formatting type changes.

     

    Any help in resolving this issue would be appreciated.

    Thank-you.

     

     

     

     

  2. Niko
    Admin
    Niko avatar
    387 posts

    Posted 08 Mar Link to this post

    Hello,

    We are aware of this issue. Please, follow this feedback item - http://feedback.telerik.com/Project/108/Feedback/Details/88678-when-accepttrackchanges-method-is-being-used-from-the-code-behind-inline-forma, for updates on resolution and estimations.

    Regards,
    Niko
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. tlp
    tlp avatar
    33 posts
    Member since:
    Oct 2006

    Posted 08 Mar Link to this post

    Hello Niko,

     

    Thanks for the post. The client-side method was implemented as recommended in the feedback item and all worked well. Looking forward to the Q2 2016 in which the issue will be resolved.

     

    Thank-you.

Back to Top