I'm currently working on a phpWebSite themes series called "HyperSpeed" (see HyperSpeed Theme) and found a little strangeness with it in Internet Explorer 7. Not sure where to post it, so please feel free to move it somewhere else.
In FireFox 1.5 and Opera 9.1, the themes look the way they should. But in Internet Explorer 7.0, I get a gray margin of 17 pixels height before the actual content which I don't want. There used to be some kind of Internet Explorer warning about a needed plugin there (which I don't understand as I'm not using any embed-statement). Apparently, I've clicked that away, now only the gray area is to be seen.
Here's how it looks in FireFox 1.5:
And here's how it looks in Internet Explorer 7 (note the gray bar between the IE chrome and my theme)
And yes, the page seems to validate according to Firefox HTML Validator plugin 0.7.9.5.
So in a nutshell:
a) how can I get that gray area away?
b) how can I stop IE 7 from requireing a multimedia-plugin for my theme?
c) also: any idea how to install a IE 6 standalone version? I couldn't find a working link...
Thanks for any help,
Fix your invalid html first.
Fix your invalid html first. CSS depends on valid html or xhtm and if you don't feed it that you have no basis to complain about the results. This may or may not fix your problem all by itself, but it is a prerequisite that you give us valid html or xhtml to work with for diagnosis, so get to work.
Also why the transitional doctype? It should be strict for any new page.
Well, as I wrote: The
Well, as I wrote: The Firefox HTML Validator Plugin says it's valid. How did you test it, which result did you get, what's wrong?
ok, correction: it didn't
ok, correction: it didn't validate with the W3C validator, just checked that. I've fixed the validation issues. But it still shows the gray area in IE7... Will try the strict doc-type.
*edit* tried strict and don't like it. Would have to ditch things like width="xyz" in TDs, that would break compatibility with older browsers... Well, the page validates transitional. What's next?
OK That tracker image you
That tracker image you have at the top, add some style to it (display:block) will do it.
rck wrote:*edit* tried
*edit* tried strict and don't like it.
Well I can't make you want to write modern code that is reasonably future proof but you can't do that without writing in strict. That's why they invented srict - it's the version of html the W3C wants you to use.
Would have to ditch things like width="xyz" in TDs, that would break compatibility with older browsers... Well, the page validates transitional. What's next?
Yeah you'd have to ditch bad past practices. But no you wouldn't have to sacrifice much in the way with compatibility with older browsers. That's just your erroneous conclusion.
What's next is to use a strict doctype unless you are transitioning a page already written in a previous version of html.
ClevaTreva, that's pure
ClevaTreva, that's pure genius -- it worked! Thanks a bunch. Moved the tracker stuff into one of the TDs, where it wouldn't harm anyone... Have to be more careful with that.
Ed Seedhouse, phpWebSite itself (the CMS behind all that) only validates Transitional. As soon as I switch to Strict in my theme, it won't validate with any given theme. I would have to do templates for all of the modules (which are quite a lot).
While the basic approach is understandable and would work for me, I don't have a business case for that. I simply cannot do tons of templates for a single theme... On the other hand, there's phpWebSite 1.0 (I'm using 0.10.0 because of the available modules). Who knows, maybe one day it will validate Strict? I'll reinvestigate then.