>> In other words sharing a problem you should solve with the visitors. <<
Nothing was shared except solutions mate - I realize the thought that
framesets might be useful has shocked you - but it's true! lol
In our situation we had a really nasty application integrity problem.
Here's the problem -
1. Online system for a leading car manufacturer
2. Some users (car dealerships in very remote locations) on < 64k
connections
3. If users click before page fully loaded, they get a event validation
exception (bug in .NET framework 2.0)
4. Connections are not 100% robust / some pages don't get there
5. Business wants a 100% bullet proof solution
So, using a frameset to marshal / handle weird partial load issues in
the inner page gave us an easy
**standards compliant** solution to the problem.
The end result is optimal user experience, even for this sad minority of
Outback Ute sellers, and that's what pretentious utopian HTML snobbery
is all about - loving your visitors.
: )
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
