|
|
Posted by Andy Dingley on 06/18/23 11:58
richard wrote:
> What I can't understand is why firefox refuses to render the page correctly
> as IE does and the editor (acehtml).
I haven't even looked at your page, but dollars to doughnuts FF is
right, IE is wrong, and the code isn't valid.
> So enlighten me and help me get back on track of doing this right.
Enlighten us first - tell us the URL. Fragments don't cut it because
for any non-trivial error, we need to see what the server is saying
too.
> <?xml version="1.0" encoding="windows-1252"?>
Don't use an XML prolog on web content
Don't use a Windows codepage on web content
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
> "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml">
Don't use XHTML unless you know what you're doing and why.
Don't use XHTML 1.1
Don't even think about writing XHTML without validating it.
> <head>
If you insist on using XHTML, do it right.
> <style type="text/css">
>
> #container
>
> #top
> {
This is probably a typo for "#top" when what you've actually coded as a
selector is "#container #top" However it shouldn't actually hurt in
this case, and may even be intended.
> width="100%"; height="140px";
Don't quote property values in CSS, I haven't tested this, but I
imagine Firefox is correctly rejecting this incorrect code, whilst IE
is attempting to auto-fix it up. I suspect this is the problem that's
actually causing trouble.
For all the rest, search the ng archives.
Navigation:
[Reply to this message]
|