Hi guys,
Quite hard to explain, but I will try ...
We have in one of our projects a really strange bug. We drag'n'drop a dock to a zone, we "close" it (close for us means move the dock to a specific zone, with a different state ... so instead of close, I should use move). Once done, we can click on the dock titlebar, so the dock moves to its last position.
The bad news is that we have no idea where it comes from, and it is quite hard to understand !
The good news is that the bug is easy to reproduce on the online demo, and I got the good idea to make a video : http://www.youtube.com/watch?v=zUVYzm_rh00
Any ideas ? Real bug or bad usage of the client-side API ?
Note : bug visible on Firefox 3.5 for sure, sometimes (to be defined) on internet explorer (unknown for other browsers)
Link to the demo : http://demos.telerik.com/aspnet-ajax/dock/examples/clientsideapi/defaultcs.aspx
Quite hard to explain, but I will try ...
We have in one of our projects a really strange bug. We drag'n'drop a dock to a zone, we "close" it (close for us means move the dock to a specific zone, with a different state ... so instead of close, I should use move). Once done, we can click on the dock titlebar, so the dock moves to its last position.
The bad news is that we have no idea where it comes from, and it is quite hard to understand !
The good news is that the bug is easy to reproduce on the online demo, and I got the good idea to make a video : http://www.youtube.com/watch?v=zUVYzm_rh00
Any ideas ? Real bug or bad usage of the client-side API ?
Note : bug visible on Firefox 3.5 for sure, sometimes (to be defined) on internet explorer (unknown for other browsers)
Link to the demo : http://demos.telerik.com/aspnet-ajax/dock/examples/clientsideapi/defaultcs.aspx