Recent Windows Update causing sizing issues

57 posts, 3 answers
  1. Answer
    DonKitchen
    DonKitchen avatar
    104 posts
    Member since:
    Jul 2007

    Posted 16 Mar 2017 Link to this post

    ADMIN UPDATE

    This is a regression issue in IEhttps://developer.microsoft.com/en-us/microsoft-edge/platform/issues/11295665/

    Cast your vote by pressing the "+Me Too" button and encourage your end users to do the same if they have an account with Microsoft.

    The problem with the RadWindow appearance will be fixed when Microsoft roll out a fix.

    Cumulative updates through Windows Update should resolve the issue. First reported updates:

    Fault condition description:

    • IE is in some form of compatibility mode (IE8, IE9 or IE10), usually via an X-UA Compatible meta tag. The issue does not manifest in standards (Edge) mode. Add a meta tag to enforce it.
    • RadWindow is in Classic RenderMode. It uses tables to render. Using the Lightweight RenderMode should alleviate the problem.
    • The end user machine has the KB4012204 update installed. Other updates that have been reported as associated with this issue: MS17-006, KB4012215, KB2952664, KB3216755, KB4013429, KB3218362

    END UPDATE

    The recent Microsoft Windows Update seems to be causing issues for us with our Radwindows.

    https://support.microsoft.com/en-us/help/4012204/ms17-006-security-update-for-internet-explorer-march-14-2017

    Attached is an example of what's happening since this update was pushed down.

    Any suggestions on a quick fix?

    Clients are IE 11 using Compatibility mode (v8).

     

     

  2. DonKitchen
    DonKitchen avatar
    104 posts
    Member since:
    Jul 2007

    Posted 16 Mar 2017 Link to this post

    Seems to happen regardless of compatibility mode or not in IE 11, FYI.
  3. Chris
    Chris avatar
    7 posts
    Member since:
    Aug 2015

    Posted 16 Mar 2017 Link to this post

    We've been trying to deal with this same issue most of the day too. A coworker has put in a support ticket but no response yet. In my case it's not causing the issue running in IIS locally but it is on the web servers. We also have one site out of 20 that's working fine and has exactly the same code except a few cosmetic things as a site that's having the problem.
  4. DonKitchen
    DonKitchen avatar
    104 posts
    Member since:
    Jul 2007

    Posted 16 Mar 2017 in reply to Chris Link to this post

    Well, not that I'm happy you're having issues but I am glad to know I'm not alone.  I will put in a support ticket also, which may help up the priority on this!
  5. DonKitchen
    DonKitchen avatar
    104 posts
    Member since:
    Jul 2007

    Posted 16 Mar 2017 in reply to Chris Link to this post

    Is yours IE 11 only also?  What else can you tell me about your user's experiencing the issue so that we can draw some similarities here?
  6. DonKitchen
    DonKitchen avatar
    104 posts
    Member since:
    Jul 2007

    Posted 16 Mar 2017 in reply to Chris Link to this post

    Chris said:We've been trying to deal with this same issue most of the day too. A coworker has put in a support ticket but no response yet. In my case it's not causing the issue running in IIS locally but it is on the web servers. We also have one site out of 20 that's working fine and has exactly the same code except a few cosmetic things as a site that's having the problem.

    Not that you want to go and change all your code (like I don't), but we've discovered that by changing the window to render in "Lightweight" mode it seems to fix the issue, or at least it's a workaround.

    Attached is a sample of what I mean.

     

     

  7. Chris
    Chris avatar
    7 posts
    Member since:
    Aug 2015

    Posted 16 Mar 2017 in reply to DonKitchen Link to this post

    I can only verify IE11 for sure. Thanks for letting me know that. I can test out changing that in our skin file and hopefully only change it in one place.
  8. DonKitchen
    DonKitchen avatar
    104 posts
    Member since:
    Jul 2007

    Posted 16 Mar 2017 in reply to Chris Link to this post

    Good call on the skin.  We didn't have one for the Radwindow but I added one with just that property and it seems to do the trick.  It's out in our TEST environments now pending release.
  9. Nick
    Nick avatar
    2 posts
    Member since:
    Mar 2017

    Posted 16 Mar 2017 Link to this post

    Does anyone know what update is causing this?  My application is running an older version of telerik and I can't get it to run in lightweight mode.
  10. Chris
    Chris avatar
    7 posts
    Member since:
    Aug 2015

    Posted 16 Mar 2017 in reply to Nick Link to this post

    It think it was https://support.microsoft.com/en-us/help/4013429/windows-10-update-kb4013429 for me. I installed 13 updates this morning and it looked the most likely to cause it.

    This appears to be the the one if you're still on Windows 7: https://support.microsoft.com/en-us/help/4012204/ms17-006-security-update-for-internet-explorer-march-14-2017

  11. Chris
    Chris avatar
    7 posts
    Member since:
    Aug 2015

    Posted 16 Mar 2017 in reply to DonKitchen Link to this post

    Even with the lightweight rendering fixing it for most people we're still having one customer using IE 11.0.9600.18617 on Windows 7 have the same problem on 3 of his computers even after running IE in safe mode and resetting. Other people with the same configurations work fine.

    This windows update is causing a lot of issues including breaking Microsoft Dynamics: http://www.infoworld.com/article/3181497/microsoft-windows/confirmed-windows-10-update-kb-4013429-breaks-microsoft-dynamics-crm-2011.html

  12. Nick
    Nick avatar
    2 posts
    Member since:
    Mar 2017

    Posted 16 Mar 2017 in reply to Chris Link to this post

    On windows 7 using IE 11.0.9600.18537 it looks like it's actually kb412204, or a combination of the two anyway.  
  13. Marin Bratanov
    Admin
    Marin Bratanov avatar
    4050 posts

    Posted 17 Mar 2017 Link to this post

    Hi guys,

    I am pinning this thread to the top of the forum so everyone can easily monitor the progress of this issue.

    We are currently investigating (thank you for submitting the tickets). We will get back to you there and we will also post information here as soon as we have it.

    Regards,

    Marin Bratanov
    Telerik by Progress
    Try our brand new, jQuery-free Angular 2 components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
  14. Richard
    Richard avatar
    1 posts
    Member since:
    Sep 2015

    Posted 17 Mar 2017 Link to this post

    Thanks for the update. One of our internal users noticed this issue the other day, but we were thinking it was just his computer as nobody else internally was having the problem. Then our customers started reporting it, and today one of our biggest customers must have gotten the update rolled out to all of their users and has been getting reports all morning.

    This is a pretty huge issue for us, hopefully you can find a fix to the problem quickly. I just think it's crazy that a security update can affect something so basic and seemingly unrelated as content height within a window!

  15. Marin Bratanov
    Admin
    Marin Bratanov avatar
    4050 posts

    Posted 17 Mar 2017 Link to this post

    Hi all,

    I have just updated the first post with information on the matter.

    Put shortly, this is a regression in IE and we must wait for a fix from Microsoft.


    /*Updated 

    This is a regression issue in IEhttps://developer.microsoft.com/en-us/microsoft-edge/platform/issues/11295665/

    Cast your vote by pressing the "+Me Too" button and encourage your end users to do the same if they have an account with Microsoft.

    The problem with the RadWindow appearance will be fixed when Microsoft roll out a fix.

    Fault condition description:

    • IE is in some form of compatibility mode (IE8, IE9 or IE10), usually via an X-UA Compatible meta tag. The issue does not manifest in standards (Edge) mode. Add a meta tag to enforce it.
    • RadWindow is in Classic RenderMode. It uses tables to render. Using the Lightweight RenderMode should alleviate the problem.
    • The end user machine has the KB4012204 update installed. Other updates that have been reported as associated with this issue: MS17-006KB4012215KB2952664KB3216755KB4013429KB3218362

    Updated*/ 

    Regards,

    Marin Bratanov
    Telerik by Progress
    Try our brand new, jQuery-free Angular 2 components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
  16. Chris
    Chris avatar
    7 posts
    Member since:
    Aug 2015

    Posted 17 Mar 2017 in reply to DonKitchen Link to this post

    Can you try adding this to your site's css file without the lightweight rendering and let me know if it works for you? It seems to help for us but it's not fully tested yet:

            .RadWindow div.rwExternalContent iframe {
                height: 100% !important;
            }
  17. Marin Bratanov
    Admin
    Marin Bratanov avatar
    4050 posts

    Posted 17 Mar 2017 Link to this post

    Hi Chris,

    This does not help for me. I would not expect it to, because RadWindow already has such a rule (without the !important modifier, though).

    The problem is in the IE rendering engine - IE8-10 modes have it. You should either add an X-UA Compatible meta tag with value IE=edge, or use the Lightweight mode. That is, until Microsoft roll out a fix.

    Regards,

    Marin Bratanov
    Telerik by Progress
    Try our brand new, jQuery-free Angular 2 components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
  18. Chris
    Chris avatar
    7 posts
    Member since:
    Aug 2015

    Posted 17 Mar 2017 in reply to Marin Bratanov Link to this post

    I was just curious and looking at the differences between classic and lightweight rendering modes with the IE DOM inspector and noticed the iframe on both of them had the height set to 100% with an inline style but on the lightweight mode the inline style was overridden by a style from the WebResource.axd that's just what I posted above. I thought the rendering engine might be picking that up and just have a bug with recognizing the inline style on the iframe. It actually seemed to help on one site but not consistently on others. At the moment I can't look at it any more today since lightweight rendering mode is working well enough for us.
  19. DonKitchen
    DonKitchen avatar
    104 posts
    Member since:
    Jul 2007

    Posted 17 Mar 2017 in reply to Marin Bratanov Link to this post

    The problem I've seen is that if you are less than Edge the Lightweight won't work.  It falls back to classic.

    And when we go to IE=Edge other things in our application aren't working or displaying properly!

  20. Marin Bratanov
    Admin
    Marin Bratanov avatar
    4050 posts

    Posted 17 Mar 2017 Link to this post

    Hi guys,

    @Chris - the key difference is the table the Classic mode uses. The IE bug is that the iframe in a table can no longer be 100%. Actually, not just iframes, but that's the relevant bit for us. Full details are available at the first post that I ammended.

    @Don - as of R1 2017, the Lightweight mode can be configured to not fall back to classic in compatibility modes if the X-UA header is present: http://docs.telerik.com/devtools/aspnet-ajax/controls/render-modes#lightweight-rendermode. This mode targets modern browsers, so edge mode for IE is expected.

    Regards,

    Marin Bratanov
    Telerik by Progress
    Try our brand new, jQuery-free Angular 2 components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
  21. DonKitchen
    DonKitchen avatar
    104 posts
    Member since:
    Jul 2007

    Posted 17 Mar 2017 in reply to Marin Bratanov Link to this post

    Right but X-UA header tag with IE=Edge changes you from 8-10.  We were already using that tag but had IE=8.

    IE=edge causes us display issues in other areas of our system unfortunately.

    Does that make sense now?

    Rendermode cannot work unless IE=Edge, right?

  22. Answer
    Trevor
    Trevor avatar
    1 posts
    Member since:
    Feb 2017

    Posted 18 Mar 2017 Link to this post

    A workaround might be to use absolute positioning on the .rwWindowContent css class.

    I took off the "height: 100% !important", and replaced it with "position: absolute; top: 38px; right: 15px; bottom: 15px; left: 15px". You might need to adjust the positioning slightly based on the RadWindow skin.

    It's not perfect, but it might suffice until the permanent fix is available.

  23. Marin Bratanov
    Admin
    Marin Bratanov avatar
    4050 posts

    Posted 20 Mar 2017 Link to this post

    Hi guys,

    @Don - it is possible that this header is added from several places in the app and the IE8 mode takes precedences (e.g., if added via an HTTP header rather than as a meta tag). I understand your point about the edge mode causing issues with other places of the app, yet as a general rule of thumb I would recommend using this mode whenever possible with regard to our controls. The Lightweight RenderMode may work in compatibility modes such as IE9 and IE10 but there still may be some issues.

    @Trevor - such an approach could work, but I would still recommend the Lightweight mode and/or the Edge mode of IE.

    Regards,

    Marin Bratanov
    Telerik by Progress
    Try our brand new, jQuery-free Angular 2 components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
  24. Harikrishnan
    Harikrishnan avatar
    3 posts
    Member since:
    Mar 2017

    Posted 21 Mar 2017 Link to this post

    Hi All,

         

  25. Harikrishnan
    Harikrishnan avatar
    3 posts
    Member since:
    Mar 2017

    Posted 21 Mar 2017 in reply to Harikrishnan Link to this post

    Hi All,

    I do have the same problem and tried with the above different solutions. But its not working.

    Is there any update from Microsoft. 

    Please help us. Client has started ....$#$###$##$%$%$%$%$

  26. ana
    ana avatar
    4 posts
    Member since:
    Mar 2015

    Posted 21 Mar 2017 in reply to Trevor Link to this post

    Thank you Trevor. In my case I had to add table.rwTable to your suggestion and IE 11 is finally working!
    I added the following to the master page:
        .rwWindowContent {
                position:absolute;
                top: 10px;
                right: 5px;
                bottom: 5px;
                left: 5px
            }
               table.rwTable{
               height:350px !important;
            } 
    We are using an old version of Telerik controls (2011.2.712.40).
  27. Charlie
    Charlie avatar
    6 posts
    Member since:
    Mar 2011

    Posted 21 Mar 2017 Link to this post

    Here's something that worked for me and wasn't too painful.  

    In the .aspx that's opened by the RadWindow, I have this:

            $(document).ready(function () {

                parent.resizeRadWindow("RadWindow1");
            });

    * "RadWindow1" is the name of my RadWindow -- sorry, not too creative on that one.

    In my parent page (that opens the RadWindow), I have this:

                function resizeRadWindow(windowName) {
                    $('[name="' + windowName + '"]').css({'height':($(".rwTable").height()+'px')})
                }

    All my parent pages have the same master page, so I only have this in one place.  Yes, you have to add JavaScript to basically every RadWindow, which may not be practical for everyone.  Also, I have only tested this with RadWindows that are opened client-side.

  28. Harikrishnan
    Harikrishnan avatar
    3 posts
    Member since:
    Mar 2017

    Posted 22 Mar 2017 Link to this post

    Its worked . NO TIME TO WAIT FOR MICROSOFT :)

    <asp:HyperLink ID="lnkSelect" runat="server" CssClass="PageHeadlinePortal" Style="font-size: 11px"
                                        EnableViewState="False" Text="Select Member" NavigateUrl="javascript:ShowDialogFromLink();"
                                        Visible="true"></asp:HyperLink>

    function ShowDialog() {
                 document.getElementById('hidMenuIdLink').value = "1";
            var oRadWindowManager = $find("<%= RadWindow.ClientID %>")
            var oWnd = oRadWindowManager.open(null, "UserListDialog");
        }

     <asp:ScriptManager ID="ScriptManager1" runat="server">
                        </asp:ScriptManager>
                        <telerik:RadWindowManager ID="RadWindow" RenderMode="Lightweight" runat="server" Overlay="false" ReloadOnShow="true"
                            Behavior="Close, Move" Modal="True" VisibleStatusbar="false" Skin="Black">
                            <Windows>
                                <telerik:RadWindow  ID="UserListDialog" runat="server" Width="550px" Height="580px"
                                    Title="User List Dialog" NavigateUrl="~/selectionlist.aspx" />
                            </Windows>
                        </telerik:RadWindowManager>

     

     

     

     

     

    css

    iframe[name='UserListDialog']

    {
    min-height: 520px !important;
    }

     

     

  29. Tim Black
    Tim Black avatar
    18 posts
    Member since:
    Nov 2002

    Posted 22 Mar 2017 Link to this post

    We just completed a Microsoft patch cycle and users are reporting issues.  So far, they all seem to relate to the <iframe> object rendered for a RadWindow.  Specifically, the height attribute rendered is set to 100% it no longer fills the parent container.  It must be set to a literal height "200px".

  30. Tim Black
    Tim Black avatar
    18 posts
    Member since:
    Nov 2002

    Posted 22 Mar 2017 in reply to Tim Black Link to this post

    Also meant to include that the issue doesn't occur with Chrome or FireFox.
Back to Top