Ken wrote:
Hi guys, this is Ken, the op (original poster), clarifying.What I reported in my original post ('another less-than-brilliant thing with SM 2.2') was IN ADDITION to other SM 2.2 woes that I and others had already reported in preceding threads. Anyway, the short of the matter is that I have used System Restore to go back to my earlier SM version (2.0.11), and all is well again. Sure, there are security risks. But I had no alternative, given my experience of the non-user-friendly and even calamitous operations (in its Composer mode) of SM 2.2
Since I use SM 2.0.14 Composer for writing my web site this cautionary tale makes me even more certain that SM 2.2 is not for me. How can I find out whether the bugs (?) in 2.2 Composer are fixed? And other than discarding SM as my default browser altogether, what can I do about the security dangers in continuing to use 2.0.14?
By the way, please save the "never use SM Composer for web page authoring" responses as I've never had problems with it before and I wish to continue using what I'm familiar with.
-- Ken Rudolph _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
