I want to achieve the following behavior,
http://dojo.telerik.com/UNIJa
so that the window moves together with the page content during scrolling.
Here is my very simple code,
$("#OUView").kendoWindow({
pined: false,
position: { top: 400 }
});
but unfortunately the window is pinned and don't moves with the page content.
I have the newest available kendo.all.min.js
Thanks in advance!
6 Answers, 1 is accepted
The demo you have provided works as expected on my side, so I am a little confused what the desired behavior is. Please check the following video and let me know if I am missing something:
http://screencast.com/t/3x4b12Be
Regards,
Dimo
Telerik
Rank 1
Hi Dimo,
thank you!
Correct, the demo is working fine. What I just wanted to say is: the same simple code "works not on my machine".
Regardless of whether if I set pinned to false or true - the window is allways pinned when I scroll the page.
I suspect that you are not scrolling the page, but some <div> in the page. In this case the Window will not move, because it is absolutely positioned with regard to the <body> element's top-left corner, and the body does not move either.
If changing the page layout and scrolling logic is not acceptable, then another possible approach is to append the Window to the scrollable <div> and apply a position:relative style to that <div>.
http://dojo.telerik.com/UNIJa/3
If your scenario is different, please modify the demo I sent, so that I can inspect it.
Regards,
Dimo
Telerik
Rank 1
Hey Dimo,
thank you very much.
I guess, that is the solution, but I can't test it. Unfortunatelly both IE and Chrome give me "SCRIPT1014: Invalid character File: mytest.css, Line: 1, Column: 1"
for the # selector caracter.
#example {
overflow: auto;
}
.position-relative {
position: relative;
}
Rank 1
Hi Dimo,
I guess that your suggestion will correct the issue, but I couldn't test it, because IE/Chrome gives me the following css error:
"SCRIPT1014: Invalid character"
for the #-selector caracter in the css-file.
Rank 1
Hi Dimo,
the problem with SCRIPT1014 was an incorrect css-file registration.
Now it's working fine.
Thank you for all!
Tihomir