pav — 2014-07-16T23:31:13-04:00 — #1
Just noticed my footer has disappeared on a fitness site I my working on for my son and was hoping someone could tell me
what I am doing wrong because it is all validating in W3c and there is a clear:both; in footer css so I am stuck.
ronpat — 2014-07-17T00:33:30-04:00 — #2
The <object> tag is not an 'empty' tag. It should not be closed with the trailing slash, /> . It needs a </object> closing tag.
Sometimes the validator can be fooled
jeff_mott — 2014-07-17T01:38:35-04:00 — #3
Naw. We just fool ourselves. We ask the validator to check the code as if it were XHTML, but then we serve that same code over the web not as XHTML but as plain old HTML. We pretend we're using XHTML but we're really not.
pav — 2014-07-17T01:48:49-04:00 — #4
I tried adding the full tag before I posted here and it changes nothing so still stuck unfortunately- wish it were that easy!
Actually when you add full end tag W3c throws up errors regarding it haha
I think I am going to ignore the validator completely in this case with google maps and go back to the iframe to get my footer back
ronpat — 2014-07-17T01:52:17-04:00 — #5
That's really odd, because when I changed it here the footer promptly appeared. In which browser is it not appearing?
You do realize that something is pushing the footer way down the page.
The opening <object tag needs it's closing ">" before the </object> tag Give that a try.
...50024" style="width:600px;height:450px;"<font color='red'>[b]>[/b]</font></object>
pav — 2014-07-17T01:54:06-04:00 — #6
The validator detects and decides what we are using so not sure what you are talking about.
jeff_mott — 2014-07-17T01:59:54-04:00 — #7
The short answer is: The validator decides based on doctype, but browsers decide based on MIME type.
The long answer: http://www.webdevout.net/articles/beware-of-xhtml#content_type
pav — 2014-07-17T02:20:35-04:00 — #8
O M G THANK YOU!
ronpat — 2014-07-17T02:22:47-04:00 — #9
pav, the problem is a syntax error with the <object> tag. The validator does not see it. It is possible for the validator to be wrong. You can write really valid code, which this seems to be to the validator (but isn't), and it will not work properly, which is what is happening here. This code contains an error that the validator is not programmed to catch.
EDIT: :lol: looks like we cross posted. Glad you got it fixed. Sometimes the simplest things can be tricky.
ronpat — 2014-07-17T02:29:42-04:00 — #10
Thank you VERY MUCH @Jeff_Mott, for the link to the XHTML information! Much appreciated.
mittineague — 2014-10-18T18:00:31-04:00 — #11
This topic is now closed. New replies are no longer allowed.