|
|
||||||
|
||||||
| Index Link To US Private Messages Archive FAQ RSS | ||||||
| Graphics & Design Discussion Forum Post your graphics design questions/comments/ideas in here. Ask questions, post tutorials, discuss trends and best practices. Sub-forum for website accessibility and usability. |
Share Thread: & Tags
|
||||
|
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
||||
|
Normally, I'd have absolutely no use for frames or iFrames, but for a particular client's site redesign, I need them.
The problem is that they don't seem to be allowed in XHTML 1.1 strict (along with frames). The question is whether or not there's an equivalent, or if there is a way to "allow" iFrames (and for that matter, the "target=_new" attribute) outside of the "hack" of creating a Javascript using innerHTML to create the iFrame.
__________________
Toronto Web Design | Search Engine Friendly, Standards-Compliant Layouts | Walk on my Path (my blog) |
|
|||
|
Both the target attribute and iframes have been dropped in XHTML1.1.
From a quick Google I found the following which basically uses an object instead of an iframe: <object type="text/html" data="http://www.google.com" width="400" height="500"> Alternate text</p> </object> Although this works in Firefox it doesn't seem to want to work in IE (SP2), I've not spent any time on this so there might be an easy fix. I'd either go to a DOCTYPE that supports iframe or use a server side script to populate the area. Hope that's some help. |
|
||||
|
Do you need the iframe to pull in content from another page?
Or is it being used to save space in your page layout? If it's the latter, then BeforeTheDog's iframe mimics might prove useful. If it's the first option, then XHTML Transitional will accept iframes. Paul |
|
||||
|
http://www.kastlefireplace.com/frame...ype=1&PID=1016
That's the idea behind it. So I guess the answer is #1. Of course, this being the only semi-practical use I've ever seen for an iFrame, I can see why they were dropped in 1.1. But if I go XHTML Transitional, won't that cause problems down the road if/when XHTML gets "upgraded"? That's why I'm leaning more toward a Javascript hack. I like the idea of going to a manufacturer's page from a product page, but within the site itself so it doesn't get lost. The DIV idea would be cool, except for the fact that you can't (to my knowledge) load external site content into a DIV.
__________________
Toronto Web Design | Search Engine Friendly, Standards-Compliant Layouts | Walk on my Path (my blog) |
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|
|
WebProWorld |
Advertise |
Contact Us |
About |
Forum Rules |
MVP's |
Archive |
Newsletter Archive |
Top |
WebProNews
WebProWorld is an iEntry, Inc. ® site - © 2009 All Rights Reserved Privacy Policy and Legal iEntry, Inc. 2549 Richmond Rd. Lexington KY, 40509 |