Hi Frank
This is an ongoing path of improvement with DotNetNuke and we have gone a long way since the early days - that's for sure, but we're not there.
In reference to a couple of things - I know developers have created a Mac friendly environment and it does take a few changes and some money out of your pocket in some instances. I know this because a couple of people here (probably more but only a couple I know of and talk with) are managing / developing school portals and guess what - they have macs... varying in age and had to resolve a few things.
Firstly - 5.2 and Mac - it's disappointing but Microsoft simply stopped supporting them a long time ago and most browser standards these days are IE 5.5 and above, that's what DotNetNuke supports (to my knowledge based on reading something but can't remember where OK) Now, to get around that, the biggest issue has been for those using the SolPart Menu - and while it's improved dramatically, it's still not a 100% solution but you can look at products like third party menus - http://www.inventua.com - that site is w3c compliant. http://www.oliverhine.com - now he's got a menu / site map that is using a third party product - from http://www.devmansion.com which allows you to build Mac friendly right back to Netscape 4.0 (I think) menu compatibility. These are just a couple of instances where they have overcome the mac issue.
Secondly - Editors - I notice the FTB editor - while not a fan of it has improved over time but you can move to the FCKEditor and get some better compliance there. Or if it's really important, then there are the http://www.telerik.com or http://www.cutesoft.net editors - sure they cost but they will solve your problem.
Thirdly - IFrame - forget using it. If something is a problem, then remove it from use in the portal - or hide it as a premium module. This is a commonly known problem not just for Macs but for early versions of Netscape and Firefox. I know there is much better support for Firefox these days and surely a Mac user can upgrade to this.
This is an open sourc environment where we work with the resources we have here. There were no Mac developers jumping in and helping in the beginning, however, not long ago, I know that a few people who bitterly complained about the lack of SolPart menu support, chipped in and provided Jon Henning with a Mac computer - it added alot to his work load but he made significant changes and could test these problems out since he now has a Mac for testing. It was a generous gesture of people assisting those developers here who are going out of their way.
Lastly - I've been doing this for few years now - back in the days of DNN1, and I have no problems developing sites with DotNetNuke knowing that there is never every going to be 100% happy people. It's not DotNetNuke I've learnt -it's people in general. I'd also like to mention that those with earlier browsers are going to have a miserable time in most areas on the internet, I've experienced that using the variety of browsers myself and honestly I'd go mad trying to make my site compatible with Netscape 2 (and yes, they appear on my logs)
I think what you need to do is look at if DotNetNuke is really for your audience. If it's a problem, then there are other good applications that might suit your requirements where you feel you don't have to compromise the browser compatibility. This is not ignoring that there is a problem or brushing it off, but it's merely stating - we're doing what we can, with the resources available, have seen some good Mac orientated sites running in school portals where they have overcome the problems. Yes it's cost them money for the third party providers, but they loved what DotNetNuke could offer them.
Third party providers are those prominent and most used areas - like the menu and editors at this stage, that allow you to put independent products that have been wrapped to work within the DotNetNuke framework and solve problems or provided enchancements, specific to a client's / users needs.
You're not telling us anything we're not aware of, and I use to try and defend DotNetNuke for it's merits, but these days - I know how good this product is, and I know how many simply brilliant developers there are picking up this framework and thinking WOW, I can do so much with it, they are using their skills to find solutions, and in the process growing it to be the fantastic product that it is.
I hope this educates you to finding something good about DotNetNuke. I also run a Linux Server, I'm solutions oriented, not tied into something so blindly that I can't see further. And I look, every day there's something new I learn, and the more I learn, the more I realise just how cool this product is... warts and all.
Just out of curiosity - was there anything you liked at all?
Nina Meiers