Mac issues?

Are there any Mac users who have had any problems using MODx?

I was just talking to a client who is having problems accessing the manager area on a Mac. I don’t see any reason for there to be any problems with MODx and Macs, but just wanted to check to see if there were any known issues. I’ve already searched the forum and didn’t really find anything.

Thanks.

Quite a number of us use Macs. Safari seems to have a few relatively minor issues with the Manager; I can’t say much about that since I use FF.

Firefox definitely has no problems on the Mac. Older versions of Safari can be troublesome and forget IE Mac entirely.

Safari 3 is not fully baked and therefore are issues with nearly all Rich Text Editors. Never heard of any Mac issues though.

I’m a Mac user and so are some of my clients. Whether they’re using PC or Mac, in the documentation I give my clients, I tell them to ONLY login to the manager area with FireFox. I’ve used Safari and it’s got some minor glitches. As far as IE Mac...forget about it. Camino has the issues as Safari.

Mac all the way and don’t have any issues. I use FF so I can’t say much for Safari, but I have used it with no problems just not heavily. I also recommend that my clients use FF since it is the only true widely used multi platform browser.

I was just talking to a client who is having problems accessing the manager area on a Mac.

Need to be more specific about the problem. Safari has a few issues with fonts that will show up as fractions (I think that it is a problem with the Helvetica Fractions font or something like that). Deactivate this font and all reads well. This is the only problem I have had with safari.

From another thread I started...

***

Safari 3 that now comes with Leopard might be different...

On my system with Safari 2.04 with Tiger the following are unavailable within the TinyMCE editor:

* Undo and Redo
* Link and Unlink
* Outdent
* Edit CSS Style

The rest of the editor seems to work fine...

The whole reason Safari 3 was shipped incomplete (in the eyes of the Webkit team) was that Apple wanted to include Safari 3 in Leopard. Recent nightly versions from Webkit have fixed this. I read that this week they even created a new benchmark for Js libraries. Sounds promising for Safari 3 in future releases.