I’d like to ask about using frames in a modern intranet-only web application.
Of course there a several reasons to use or probably not use frames in a modern internet web application.
But what about when it comes to an intranet web applications (think about a financial application)?
Think about parts of the application which are most of the time constantly visible (like a toolbar, menu, identity et cetera), where frames can be a simple/faster solution to do things?
Are these advantages that count these days when considering things like PPR?
I am curious and both thankful about your view on this.
Frames aren’t inheritly evil, but they do create challenges that other approaches don’t face. Since you’re talking about intranet you probably aren’t concerned about:
Overall there probably isn’t an outstanding reason to dodge them. However I don’t think you’ve offered a compelling reason to use them.
However: the one issue I could see you running into with a rich internet application is the potential need for your differing pages/components to talk with one another. Frames can be a royal headache with scripting, and for that reason alone I avoid them.