[Veltliner]

(deleted)

[Veltliner]

I solved that issue.

iframe uses a deprecated property name="....".

So I used id instead, which made the iframe accessible for positioning in CSS.

Safari and Opera were OK with this.

Firefox? No. It broke the iframe element. Instead of opening images in a new window, they were opened on a new page.

I added the name="..." to the id, and now it works in Firefox 3, too.

Funny. There's an element that's "deprecated" by W3, which I understand as "don't use it".

It's like chess: you against the browsers to get them to display your design.

[Mac User #001]

I've had crap luck with iFrames in Safari. I'm surprised Firefox was your problem. Anyways, good to hear you got it working.

[Oisín]

Originally Posted by Veltliner 

I added the name="..." to the id, and now it works in Firefox 3, too.

Funny. There's an element that's "deprecated" by W3, which I understand as "don't use it".

It’s formally deprecated and will be removed in the next version of XHTML. The W3 recommends the following:

In XML, URI-references [RFC2396] that end with fragment identifiers of the form "#foo" do not refer to elements with an attribute name="foo"; rather, they refer to elements with an attribute defined to be of type ID, e.g., the id attribute in HTML 4. Many existing HTML clients don't support the use of ID-type attributes in this way, so identical values may be supplied for both of these attributes to ensure maximum forward and backward compatibility (e.g., <a id="foo" name="foo">...</a>). [Emphasis mine]