March 14 Windows Updates Also Causing Widespread IE11 Bug
Microsoft’s March 2017 Patch Tuesday updates are slowly becoming a huge fiasco, as more and more users are now reporting issues after the install.
This time, it turns out that a Patch Tuesday update is breaking down Windows dialog boxes created with Telerik, with the company already acknowledging bugs that were reported by users.
As The Reg points out, it turns out that the cumulative update for Internet Explorer that was released this month is breaking RadWindow and RadListBox, with Telerik advising customers to switch to Microsoft Edge or adopt some other workarounds, such as the Lightweight Render Mode or replacing the div tag with span in website templates.
Microsoft is reportedly aware of the problem and is already developing a fix, though it’s not yet clear when this could be released. It’s possible that Microsoft waits until the next month’s Patch Tuesday to address the bugs, or the company could also launch a new cumulative update in the meantime with this purpose.
"No ETA just yet"
Earlier this week, the company published a new cumulative update for Windows 10 Anniversary Update computers that fix problems experienced after installing the March 14 updates.
“Bugs like this are common occurrences when tweaks are made to a browser. We have identified and reported the issue to Microsoft, who is addressing it and will provide the fix,” a Telerik spokesperson was quoted as saying by the source mentioned above.
Microsoft has already confirmed a bug in IE11, but the company says that it’s only experienced when running the browser in IE8 compatibility mode.
“The latest IE11 security update KB4012204 introduces a regression bug (maybe due to included fix KB4015241) with element height calculation in table cells in IE8 compatbility mode / DOCTYPE HTML 4. If an element has its height set to 100% and the parent table / row / cell has an explicit or inherited height, then the element should size itself to the parent cell instead of only to its content,” it says.
For the moment, there’s no ETA as to when the fix could be shipped to users, but given that the issue is public and Microsoft is already aware of it, we shouldn’t wait too long before getting it.
http://news.softpedia.com/news/march-14 ... 4159.shtml
Place you can talk about other things not related to autopatcher.
1 post • Page 1 of 1
- Release Maintainer
- Posts: 1967
- Joined: Mon Oct 28, 2013 10:47 am
- Location: Australia
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"