Reportviewer IE 11

7 posts, 0 answers
  1. Ken
    Ken avatar
    23 posts
    Member since:
    Oct 2012

    Posted 13 Jan 2014 Link to this post

    Very simple form with only a blank report
    With FormDecorator the report viewer export drop down box is disabled or does not work when FormDecorator  is removed all works fine.
    This only happens in IE 11
    If I add ControlsToSkip="Select" to the FormDecorator markup then all is good in IE 11 

     

    <body>
        <form id="form1" runat="server">
        <telerik:RadScriptManager ID="RadScriptManager1" runat="server">
            <Scripts>
            </Scripts>
        </telerik:RadScriptManager>
            <telerik:RadFormDecorator ID="RadFormDecorator1" runat="server" DecoratedControls="All" />
        <telerik:ReportViewer ID="ReportViewer1"  Width="800"  runat="server"></telerik:ReportViewer>
        </form>
    </body>
  2. Danail Vasilev
    Admin
    Danail Vasilev avatar
    1494 posts

    Posted 16 Jan 2014 Link to this post

    Hi Ken,

    This seems to be an issue with the decorated select of the ReportViewer in IE11. I have logged the issue in our feedback portal here, so that you can monitor, comment or raise its priority by voting on it.

    For the time being you can either skip the selects elements from decoration:
    ASPX:
    <telerik:RadFormDecorator ID="RadFormDecorator1" runat="server" DecoratedControls="All" ControlsToSkip="Select" />
    <div id="div1">
    <telerik:ReportViewer ID="ReportViewer1" runat="server" Height="492px" Width="927px"></telerik:ReportViewer>
    </div>

    Or decorate only particular zone that do not include the ReportViewer:
    ASPX:
    <telerik:RadFormDecorator ID="RadFormDecorator1" runat="server" DecoratedControls="All" DecorationZoneID="div2" />
    <div id="div1">
    <telerik:ReportViewer ID="ReportViewer1" runat="server" Height="492px" Width="927px"></telerik:ReportViewer>
    </div>
    <div id="div2">
    <input type="text" name="name" value=" " />
    <select>
    <option>option1</option>
    <option>option2</option>
    <option>option3</option>
    </select>
    </div>

    I have also updated your Telerik points for reporting this issue to us.

    Regards,
    Danail Vasilev
    Telerik
    Explore the entire set of ASP.NET AJAX controls we offer here and browse the myriad online demos to learn more about the components and the features they incorporate.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. IT Manager
    IT Manager avatar
    11 posts
    Member since:
    Jan 2011

    Posted 16 Jan 2014 Link to this post

    I am not sure why we have to vote on something to get fixed that is obviously broken...
  5. Ken
    Ken avatar
    23 posts
    Member since:
    Oct 2012

    Posted 16 Jan 2014 Link to this post

    Vote.  Crazy. How about just fix it
  6. Danail Vasilev
    Admin
    Danail Vasilev avatar
    1494 posts

    Posted 17 Jan 2014 Link to this post

    Hello All,

    I have raised the priority of this issue and escalated it to the attention of our developers. However, I cannot provide any firm ETA when the issue will be fixed because the tasks for this Q have already been planned.

    Regarding the voting on feedback items - since we have many requests about fixes, improvements and feature requests we let our customers decide which are the most important/desired ones by voting on them. Thus the feedback items that receive higher votes will also receive higher priority over the rest. That is why I have suggested that  you vote on the provided item.

    Regards,
    Danail Vasilev
    Telerik
    Explore the entire set of ASP.NET AJAX controls we offer here and browse the myriad online demos to learn more about the components and the features they incorporate.
  7. Dennis
    Dennis avatar
    15 posts
    Member since:
    Feb 2009

    Posted 11 Mar 2014 Link to this post

    Danail --

    I agree with Ken & IT Manager that this needs to be fixed.  I use an architecture where the RadFormDecorator is in the Master Page and the ReportViewer is in the child page.  To get around the problem, I used the following code in the Master Page code-behind

    '
    ' FIX THE ERROR IN Q1 2014 TELERIK REPORTVIEWER AND RADFORMDECORATOR
    '
    If sender.Page.AppRelativeVirtualPath = "~/Report.aspx" Then
        RadFormDecorator1.ControlsToSkip = Telerik.Web.UI.FormDecoratorDecoratedControls.Select
    End If

    Now, I could further test for IE11 but part of the reason we use the Telerik Controls is so we don't have to get into browser specific issues.

    This is an obvious hole where a test needs to be added to cover the combination of RadFormDecorator and ReportViewer.

    Sincerely,
    Dennis
  8. Danail Vasilev
    Admin
    Danail Vasilev avatar
    1494 posts

    Posted 14 Mar 2014 Link to this post

    Hello Dennis,

    Thank you for your feedback.

    The mentioned issue with the RadFormDecorator has been fixed in Q1 2014 (see the feedback item). If you are not using the latest official version of Telerik UI for ASP.NET AJAX - 2014.1.225, does upgrading to it fixes the issue?

    If the above step, however, doesn't help could you please try to reproduce the issue with the attached VS example and tell us what changes you have made, so that I can make an investigation locally? You can also watch a short video test that the decorated select from the reporting is working properly on my side in IE, Chrome and FireFox. The used versions of the testing were:
    • Telerik UI for ASP.NET AJAX - 2014.1.225
    • Telerik Reporting - 7.2.13.1216.


    Regards,
    Danail Vasilev
    Telerik
     
    Explore the entire set of ASP.NET AJAX controls we offer here and browse the myriad online demos to learn more about the components and the features they incorporate.
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017