As a new member of this forum, I want to thank everyone in the community for taking the time to help a stranger with an almost impossible problem.

Within a few hours of making my first post, some took the time to review the problem, and within a few days dozens more did the same. To all I extend my most sincere thanks.

However, to this point, the problem solution seems to lie outside the combined expertise of our entire community.

I believe that's because the two major players in this drama, Google and Apple, are natural born competitors and, more importantly, their browser offerings (Chrome and Safari) are built around the WebKit open software browser engine.

Having these three cooks in the same kitchen is a natural recipe for software maintenance disaster. Almost surely, this triangle will detract from the fine work of the WebKit open source community.

Perhaps this post about fixing a bug in an image map is a good example. As far as I can tell, it was reported to the WebKit project over four years ago and still holds a level two priority.

Meanwhile Chrome and Safari built their shells around it, captured a significant browser market share, and now are unable or unwilling to even admit that any problem exists or advise the submitters of problems how to track the progress.

So for web developers to keep their good reputation under these circumstances, it seems like there is only one counter productive solution available - alert the user at the time when a site accessed that the browser being used has bugs that will detract from their viewing the website.

Perhaps this bad publicity might encourage the big players to take some more effective action on fixing identified bugs and perhaps compensate the WebKit project for their extra effort on their behalf.

Anyhow, thanks again to all for looking at my problem and listening to my rants.

Best regards to all...Bob Lennon