Hey Telerik,
Just a quick question. I experienced a pretty curious bug under Internet Explorer.
The web application I'm building upon has a Master Page which defines some a horizontal navigation bar at the top of the page.
After opening a RadWindow with Content Template, then closing the RadWindow, the horizontal navigation bar becomes invisible. This only occurs on Internet Explorer, only with Content Template RadWindows, and only if they are Modal.
I was especially careful to go through all of my code and make sure there were no early terminations of HTML mark-up controls. That is, something like
would not be acceptable due to the parsing standards of IE. As such, I am confident in saying that I am properly terminating my HTML mark-up.
That being said, I was able to resolve the issue like so:
Which is awesome -- I am happy to have fixed the bug. Nevertheless, I am left very curious. What's going on here? Why would this implementation have better results than setting the Modal property explicitly?
Thanks,
Sean
Just a quick question. I experienced a pretty curious bug under Internet Explorer.
The web application I'm building upon has a Master Page which defines some a horizontal navigation bar at the top of the page.
After opening a RadWindow with Content Template, then closing the RadWindow, the horizontal navigation bar becomes invisible. This only occurs on Internet Explorer, only with Content Template RadWindows, and only if they are Modal.
I was especially careful to go through all of my code and make sure there were no early terminations of HTML mark-up controls. That is, something like
<
div
id
=
"foo"
/>
would not be acceptable due to the parsing standards of IE. As such, I am confident in saying that I am properly terminating my HTML mark-up.
That being said, I was able to resolve the issue like so:
OnClientBeforeShow = "AddModal";
OnClientBeforeClose = "RemoveModal";
//Bug -- IE removes 'TopBar' when closing a modal, content template RadWindow. Circumvent by removing the property right before close.
function
AddModal(radWindow) {
radWindow.set_modal(
true
);
}
function
RemoveModal(radWindow) {
radWindow.set_modal(
false
);
}
Which is awesome -- I am happy to have fixed the bug. Nevertheless, I am left very curious. What's going on here? Why would this implementation have better results than setting the Modal property explicitly?
Thanks,
Sean