×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
http://www.w3schools.com/TAGS/tag_iframe.asp
in the "Differences..." section. Says "not supported in 4.1 Strict"
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Tuesday, July 14, 2009 12:12 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] web page with data from two sources
From: Mike Cunningham
It's been depreciated by W3C ...
You may have heard about <frameset> elements being deprecated. I found some chatter in forums about deprecating <iframe> elements. But not at W3C, as far as I could find.
I use <iframe> elements in database maintenance & transaction processing applications, so I had to follow-up to make sure that they're still part of the standard.
It appears that the <iframe> "name" attribute has been deprecated in XHTML 1.0 according to the following quote, but even that is dependent on using the "strict" DTD.
"Finally, note that XHTML 1.0 has deprecated the name attribute of the a, applet, form, frame, iframe, img, and map elements, and it will be removed from XHTML in subsequent versions."
The reason I chose <iframe> elements over scrollable <div> elements was to allow the user to adjust the size of their browser window or drag a splitter bar, and have the iframes automatically adjust their height and width accordingly. That's an automatic behavior when you set an iframe's height and width to be a percent of its parent, which is useful in applications.
You can kindof see the <iframe> elements in the following screen shots. They offer a smooth transition as the user transitions from login, to menu, to applications.
http://www.radile.com/rdweb/temp/iframes.html
-Nathan
midrange.com
