Hi,
I and some of my clients who are running MacOSX and Firefox are having some issues with the asset map.
Check the attached files for the behaviors.
This happens every time we use the backend.
The capture was done on a Macbook Pro with MacOSX 10.4.8 and Firefox 2.0, I’ve also tried with Firefox 1.5.x with same result. My clients have the same issue and are running quite old Macs with Firefox 1.5.x.
Wondering is this is something that only we have and if I should post it as a bug? Can it be the JVM version?
As the clips are showing it seems to be something problems when the refresh of the whole page are taking place… time to use AJAX a bit more perhaps?
Edit: I do not have any errors in the log regarding this either.
FirefoxScreenSnapz001.mov (165 KB)
FirefoxScreenSnapz002.mov (174 KB)
Asset map on MacOSX
Yeah, this happens on OS X and Firefox. Pretty sure there is nothing we can actually do about it. It started getting worse with Firefox 1.5 if I remember, but Firefox, Java and OS X have never really played well together.
I think Safari works better with the asset map, but the WYSIWYG doesn't work.
I find myself switching to the myspace tab and back again to get it to repaint. That fixes it for a while. But you can see that stupid things like selecting a drop-down break it, so I doubt this will get fixed by any code we can change.
I’ve switched to Camino for all my Matrix work. It’s the Mozilla engine, so the WYSIWYG editor works, but it doesn’t have the Java paint issues like Firefox does. Also, it uses all the proper Cocoa buttons and stuff like Safari does.
Greg,
this seems like a issue connected to the use of the Java applet. Have you ever had thoughts of looking into using AJAX for the asset map? That would make it possible to bring a lot of more functionality to the entire backend.
Have you seen Zimbra WebUI?
The Asset Map will not be redeveloped for Matrix, but I believe the MySource4 guys are looking at alternatives. 
By the way, how is the time line looking for MySource4? Do you publish any info on any web, blog? Would be VERY interesting to follow the development process and to give feedback. Maybe Squiz could get something out of asking the users for inputs?
Just confirming that I have, and have always had this same problem on OSX.
At the moment, all of this is still internal. I don't even think the My4 team have started any work on any of the interfaces yet. They're still building the new architecture (which is awesome, btw). Once My4 is actually something you can install, we'll start considering how to get feedback from the community.
Double-posting to repeat my advice about Camino: I'm loving it on my Mac for everything now (I've pretty much dumped Safari and Firefox off my dock).
Only happens sometimes with my Firefox. For me, simply left-clicking on the area where the asset map would be correctly rendered forces it to be redrawn correctly. Camino is only marginally better than Firefox for OS X, use Safari (and Raw HTML content type) 
[quote]Camino is only marginally better than Firefox for OS X
[right][post=“12939”]<{POST_SNAPBACK}>[/post][/right][/quote]
Interesting. My experience (on Core Duo Intel MacBook Pro) is that Camino is rock solid with Matrix, far better than Firefox or Safari.
I would agree with Avi about Camino. My only problem is, I have to use another small PHP CMS for a site that I manage, and the WYSYWIG editor does not work for that CMS in Camino. I know, I should move it over to Matrix, but it is such a small site, I don't think it is worth my effort.
[quote]I would agree with Avi about Camino. My only problem is, I have to use another small PHP CMS for a site that I manage, and the WYSYWIG editor does not work for that CMS in Camino. I know, I should move it over to Matrix, but it is such a small site, I don’t think it is worth my effort.
[right][post=“12969”]<{POST_SNAPBACK}>[/post][/right][/quote]
That’s odd – Camino and Firefox use the same engine, so whatever works in Firefox should also work in Camino.
[quote]That’s odd – Camino and Firefox use the same engine, so whatever works in Firefox should also work in Camino.
[right][post=“12974”]<{POST_SNAPBACK}>[/post][/right][/quote]
I wonder then, why your Matrix experience is better with Camino than with Firefox?
[quote]I wonder then, why your Matrix experience is better with Camino than with Firefox?
[right][post=“12977”]<{POST_SNAPBACK}>[/post][/right][/quote]
Because only the rendering engine is the same. Camino (I believe) is a native Cocoa application, which suggests it handles things like talking to the native Java VM better.