I'm trying to figure out why prototype framework interferes my dojo grid component on admin helper plugin.
Problem is that if there is some editable component on dojo grid(like checkbox) and you have enough data so that scrollbar is in use(scrolled away from top). If I click the checkbox result is whole grid component render. If grid is placed on table, whole table is rendered. Result is page flickering. And since hqu content is wrapped on table, almost whole screen flickers.
This is easy tested by adding below line to dojo's test file 'dojox/grid/tests/test_tundra_edit.html'.
<script src="/js/prototype.js" type="text/javascript"></script>
I don't understand why this flickering happens if prototype is included, but never used from client code. Did some profiling using firebug and if I got it right, prototype is calling some dom events stuff during instation. On other hand, profiling doesn't show any calls to prototype when dojo table is clicked and this page flickering happens. Prototype seems to be quite funny library, since it drills down to lot of objects and does its magic instantiation. It kind of slips hands to your pockets and you need to hope it don't squeeze your balls ;)
There has been a lot of discussion about prototype interfering other javascript frameworks. Since dojo and prototype exists together almost on all pages, there may be problems also on other places.
So here is the RFE. Include dojo 1.2.3 to HQ distribution. It actually seems to pass same tests where dojo 1.1 fails.
Problem is that if there is some editable component on dojo grid(like checkbox) and you have enough data so that scrollbar is in use(scrolled away from top). If I click the checkbox result is whole grid component render. If grid is placed on table, whole table is rendered. Result is page flickering. And since hqu content is wrapped on table, almost whole screen flickers.
This is easy tested by adding below line to dojo's test file 'dojox/grid/tests/test_tundra_edit.html'.
<script src="/js/prototype.js" type="text/javascript"></script>
I don't understand why this flickering happens if prototype is included, but never used from client code. Did some profiling using firebug and if I got it right, prototype is calling some dom events stuff during instation. On other hand, profiling doesn't show any calls to prototype when dojo table is clicked and this page flickering happens. Prototype seems to be quite funny library, since it drills down to lot of objects and does its magic instantiation. It kind of slips hands to your pockets and you need to hope it don't squeeze your balls ;)
There has been a lot of discussion about prototype interfering other javascript frameworks. Since dojo and prototype exists together almost on all pages, there may be problems also on other places.
So here is the RFE. Include dojo 1.2.3 to HQ distribution. It actually seems to pass same tests where dojo 1.1 fails.