Hi Stefan, It is apparently a browser "feature": works fine in Chrome (Version 28.0.1500.95).
A side note: would "return false;" following the DOM instruction help here? Dmitry On Wed, Aug 7, 2013 at 6:59 PM, Stefan Matheis <matheis.ste...@gmail.com>wrote: > Hey Dmitry > > That sounds a bit odd .. those are more like notices instead of real > errors .. sure that those are stopping the UI from working? if so .. we > should see more reports like those. > > Can you verify the problem by using another browser? > > I mean .. that is really a basic javascript handler .. directly written in > the DOM, no chance that it doesn't get loaded. and that normally stops only > working if something really bad happens ;o > > - Stefan > > > On Wednesday, August 7, 2013 at 4:23 PM, Dmitry Kan wrote: > > > Hi Stefan, > > > > I was able to debug the second click scenario (was tricky to catch it, > > since on click redirect happens and logs statements of the previous are > > gone; worked via setting break-points in plugins.js) and got these errors > > (firefox 23.0 ubuntu): > > > > [17:20:00.731] TypeError: anonymous function does not always return a > value > > @ http://localhost:8983/solr/js/scripts/logging.js?_=4.3.1:294 > > [17:20:00.743] TypeError: anonymous function does not always return a > value > > @ http://localhost:8983/solr/js/scripts/plugins.js?_=4.3.1:371 > > [17:20:00.769] TypeError: anonymous function does not always return a > value > > @ http://localhost:8983/solr/js/scripts/replication.js?_=4.3.1:35 > > [17:20:00.771] TypeError: anonymous function does not always return a > value > > @ http://localhost:8983/solr/js/scripts/schema-browser.js?_=4.3.1:68 > > [17:20:00.772] TypeError: anonymous function does not always return a > value > > @ http://localhost:8983/solr/js/scripts/schema-browser.js?_=4.3.1:1185 > > > > > > > > Dmitry > > > > > > On Wed, Aug 7, 2013 at 4:35 PM, Stefan Matheis > > <matheis.ste...@gmail.com(mailto: > matheis.ste...@gmail.com)>wrote: > > > > > It shouldn't .. but from your description sounds as the > javascript-onclick > > > handler doesn't work on the second click (which would do a page > reload). > > > > > > if you use chrome, firefox or safari .. can you open the "developer > tools" > > > and check if they report any javascript error? which would explain why > .. > > > > > > BTW: You don't have to use that button in the meantime .. just refresh > the > > > page (that is exactly what the button does). sure, it should work, but > > > shouldn't stop you from refreshing the page :) > > > > > > - Stefan > > > > > > > > > On Wednesday, August 7, 2013 at 3:00 PM, Dmitry Kan wrote: > > > > > > > On the first click the values are refreshed. On the second click the > page > > > > gets redirected: > > > > > > > > from: http://localhost:8983/solr/#/statements/plugins/cache > > > > to: http://localhost:8983/solr/#/ > > > > > > > > Is this intentional? > > > > > > > > Regards, > > > > > > > > Dmitry > >
