Severe rendering problems

5 posts, 0 answers
  1. Bryan
    Bryan avatar
    9 posts
    Member since:
    Jan 2015

    Posted 06 Dec 2015 Link to this post

    For some time, I've noticed some severe rendering problems when using Kendo numeric/integer text box widgets. Here's the scenario:

    Currently, I'm using the latest version of everything (Windows 10 with update 1511, VS 2015 Update 1, latest Kendo), although the problems I'm seeing date back to Window 8/8.1 and VS 2013.

    I've got an MVC app using Bootstrap.

    In the particular case that I'm working on right now, I've got a form inside a dialog box (Kendo Window widget) that uses a number of different Kendo widgets for input (TextBox, DropDownList, IntegerTextBox).

    When I use the IntegerTextBox (or other numeric) widget, rendering consistently just goes all to hell in the dialog box. Spinners disappearing are the least of it. A lot of the time, all the other HTML elements in the dialog box are being overlaid by something. When I move the mouse over various controls, they sometimes appear and sometimes disappear. Clicking on one of the numeric text boxes tends to make everything else disappear. If I remove all numeric text box widgets from the form, the problems disappear completely. Removing the form itself has no impact. Removing validators has no impact.

    This occurs in both IE and Edge browsers, but only on my desktop system, never on my laptop or my Surface Pro 3. My desktop system has a second generation i7-2600 with Intel HD Graphics 2000. My laptop has a fourth generation i7-4700HQ with Intel HD Graphics 4600. My Surface Pro 3 has a fourth generation i5-4300U with Intel HD Graphics 4400. I don't see these types of problems when I surf around the web, just in the apps I'm developing with Kendo.

    I'm almost at the point of having to buy another desktop computer with a newer processor/graphics just so I can do my work. The problem with that, as my wife wisely points out, is that my customers may run into this problem with the deployed app. Judging by other forum threads, other developers are seeing similar things, but no one seems to have been able to come up with an example that you can duplicate. I suggest you get a system similar to my desktop machine and try it on that. I think the problem is related to the interaction between the Intel HD Graphics 2000, Windows 8x/10, and Kendo. Intel has essentially dropped support for their HD Graphics 2000/3000 for versions of Windows greater than 7 although, obviously, Windows 8x/10 installs and seems to otherwise work on those systems.

     

  2. Georgi Krustev
    Admin
    Georgi Krustev avatar
    3706 posts

    Posted 09 Dec 2015 Link to this post

    Hello Bryan,

    Based on the given information, I believe that the issue is related to a CSS styling that is not applied correctly. It shouldn't be related to the used hardware as the IE browser, as other ones like Chrome, Firefox, can work on different machines. This is where the OS come in to hand.

    The best way to proceed with the investigation is to build a repro demo that shows the issue. You can use our Dojo service to build a stripped repro demo: As a side note, I would suggest you examine the page using the browser web tool and more specifically the CSS applied to the HTML elements. Thus you will be able to find what is the difference in the behavior. Once again I would like to point out that the difference in the hardware is highly unlikely to be related to this issue. It could be OS + browser issue though.

    Regards,
    Georgi Krustev
    Telerik
     
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
     
  3. Kendo UI is VS 2017 Ready
  4. Bryan
    Bryan avatar
    9 posts
    Member since:
    Jan 2015

    Posted 09 Dec 2015 in reply to Georgi Krustev Link to this post

    Hi Georgi,

    This issue is absolutely tied to the hardware/driver/OS as I described. I, too, find it hard to believe, but it is. I had identical development environments set up on three different machines with exact same code (coming from TFS) and saw the behavior only on the i7 2600/HD Graphics 2000 machine. What's more, since my last post I have replaced the motherboard and processor in my desktop machine with an i5 6600/HD Graphics 530. I kept the hard drive from the old machine and, without touching the code or the development environment, just updated the drivers using the Asus driver disk that came with the Z150-AR motherboard. The problem completely disappeared.

    I don't have time to build you a web app that demonstrates the problem since I am in the middle of pushing a long term project out for UAT. I've already spent a lot of time working this issue and have given you a complete enough description of how to duplicate it. We need you to take this seriously since our customers may be impacted. If we find that they are, our only option at this point is to discontinue the use of your numeric text box widgets.

     Thanks,
    -Bryan

  5. Bryan
    Bryan avatar
    9 posts
    Member since:
    Jan 2015

    Posted 09 Dec 2015 in reply to Bryan Link to this post

    One correction: the new motherboard is an Asus Z170-AR, not Z150-AR.
  6. Georgi Krustev
    Admin
    Georgi Krustev avatar
    3706 posts

    Posted 11 Dec 2015 Link to this post

    Hello Bryan,

    In that case, the problem indeed could be related to the hardware and more specifically to the drivers that manage the video card. It seems to be related to the Windows OS and IE browser. I suppose that they cannot render some CSS rules correctly due the 3D styling acceleration, done by default in CSS3. I would suggest you also contact Windows or Intel too, as they will have more knowledge for known issues.

    What you can do on your side is to get the unminified CSS files and graduately remove CSS rules to narrow the problem down to a specific rule. This information could help us to spot the problem to a specific code line and try to find a workaround to this driver problem. 

    I can assure you that we take this issue seriously and we will continue monitor it, but I am afraid that we cannot do much on our side, as we are using standard CSS rules, which should work by specification on browsers that follows the W3C recommendations. If we found the cause in a particular CSS rule or you provide this information, then we definitely will fix it on our side.

    Regards,
    Georgi Krustev
    Telerik
     
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
     
Back to Top
Kendo UI is VS 2017 Ready