That Damn FB iframe with the obsolete attributes...revisited

SteelMan
Offline

Active Subscriptions:

None

10 years 3 months ago #40607 by SteelMan

That Damn FB iframe with the obsolete attributes...revisited was created by SteelMan

I have full validation except for the following:

<html xmlns:lipsapp="ogp.me/ns/fb/lipsapp#" xml:lang="en-gb" lang="en-gb" dir="ltr"
Priority 1
Attribute 'lipsapp' not allowed on element.
Line 3 HTML5

JavaScript added element:
<div style=""><div></div></div>
>

Priority 1
The 'allowtransparency' attribute on the 'iframe' element is obsolete. Use CSS instead.
Line 69 HTML5

Priority 1
The 'frameborder' attribute on the 'iframe' element is obsolete. Use CSS instead.
Line 69 HTML5

Priority 1
The 'scrolling' attribute on the 'iframe' element is obsolete. Use CSS instead.
Line 69 HTML5

I have tried every way I can think of and research to simply remove the 3 freaking attributes from the fb iframe including ajax with a timer, and nothing works.

Is there no way to accomplish using FBConnect AND have fully validated code? Is there no other way to get that iframe in the page than the way it is being done, which apparently makes it untouchable?

On a related note, is there no way to adjust or comment this bit xmlns:lipsapp="ogp.me/ns/fb/lipsapp#" so that it validates?

I stopped using FBConnect on the last project and wrote the parts I had to have for a client who had to have validation. I'd rather not stop using it again on this major project if it can be avoided, but I really need validation for idiots advising key investors.

Please advise.

The topic has been locked.

alzander
Offline

Support Specialist

10 years 3 months ago #40614 by alzander

Replied by alzander on topic That Damn FB iframe with the obsolete attributes...revisited

I have tried every way I can think of and research to simply remove the 3 freaking attributes from the fb iframe including ajax with a timer, and nothing works.

This may actually be removing the attribute with Javascript, but the actual HTML that was downloaded and parsed would still be invalid. So, when the Facebook Javascript loads the iframe into your page, you'd need to be able to intercept and alter that before it becomes a part of the DOM.. which is difficult, if not impossible.

Is there no way to accomplish using FBConnect AND have fully validated code? Is there no other way to get that iframe in the page than the way it is being done, which apparently makes it untouchable?

As far as I know, there's no way to do so. The allowtransparency attribute isn't a 'true' HTML attribute defined in any Doctype, so it's not like you can even change your doctype from "<!DOCTYPE html>" to something else to make it work. However, every browser in the last 10 years understands that attribute and uses it as expected.

On a related note, is there no way to adjust or comment this bit xmlns:lipsapp="ogp.me/ns/fb/lipsapp#" so that it validates?

You *could* change your DOCTYPE to something like:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

That should make the line in question validate. However, it will probably make the rest of your document not validate. Again, all major browsers understand that declaration regardless of your doctype.

I can help you remove the xmlns line if you just don't want it added at all. That's used for Open Graph Actions and Facebook Canvas integration. If you don't need that, you can live without that declaration.

As always, validation is pretty much useless. I understand your clients may care, but browsers and search engines don't, so I'd explain it hard to them about how little what they're focusing on matters.

I hope that helps, and best of luck,
Alex

The topic has been locked.

SteelMan
Offline

Active Subscriptions:

None

10 years 3 months ago #40616 by SteelMan

Replied by SteelMan on topic That Damn FB iframe with the obsolete attributes...revisited

Thanks Alex. Letting this dog lie again for now then.

The topic has been locked.

alzander
Offline

Support Specialist

10 years 3 months ago #40639 by alzander

Replied by alzander on topic That Damn FB iframe with the obsolete attributes...revisited

I understand it's frustrating. There's things that we come back to with the social networks every few months just to check if there's a better way to do something or a solution for lurking issue.. never fun, but unfortunately, there's just not anything we can do in this case.

As always, just let us know if you have any other questions or issues and we'll gladly try to help fix them (or explain why we can't!)

Alex

The topic has been locked.

Start
Prev
1
Next
End

SourceCoast Login

That Damn FB iframe with the obsolete attributes...revisited