Is it only me? (well, I know it's not, because another person reported it to me!)
When using Google Chrome (Mac) an asset 'expands' with a single click, and the 'more than 50 items' arrow buttons don't work at all.
Pretty much all my other browsers work perfectly.
Matrix 3.20.6 - latest versions of all browsers and mac Java libraries up to date.
Is there a fix other than "don't use Chrome"?
I can confirm it, which is a pity because the admin seems to be really fast in chrome on the mac. A work around would be to remove the asset limit per set restriction in the system configuration, but the setting is to get around the issues of performance and usability of the asset map when large numbers of assets are under a single root node. Incidentally, there will be a raft of other features that wont work in chrome on the mac, like the unsaved content warning you would usually get when leaving a page. This warning doesn't work on chrome on winders either but the arrows do, multi browser shenanigans abound 
Java support for Chrome is very recent, I guess they haven't got all the kinks worked out yet. If it works on another browser sharing the same JRE then the fix would have to be made for the supporting browser and not the applet itself. I think add this to the growing list of issues with java in chrome.
[quote]
Java support for Chrome is very recent, I guess they haven't got all the kinks worked out yet. If it works on another browser sharing the same JRE then the fix would have to be made for the supporting browser and not the applet itself. I think add this to the growing list of issues with java in chrome.
[/quote]
True enough, however, it's obviously only some things that don't work. It could be that the applet does these things in a way that is deprecated or maybe there are better ways of achieving the effect. This sort of thing happened with javascript as the language evolved and newer browsers dropped support for old ways of doing things. It's a pretty old codebase, I was just asking what other people had found and whether there were any updates around these problems - especially as we're not on the most recent version of matrix.
Perhaps it's just a Chrome/MAC issue as I have been using Matrix in Chrome/Windows for many months with the Java asset tree functioning normally–no problems.
[quote]
Perhaps it's just a Chrome/MAC issue…
[/quote]
Well actually, it seems to have been a Java/Mac issue - pleased to report that the latest Java update I just installed (1.6.0_22-b04-307 !) has fixed any problems I had in Chrome. Nice and fast too!