New Website (FireFox bug)
New Website (FireFox bug)
Today I designed this website. It works fine in IE but theres a glitch with the menues in FireFox. I have no idea what's causing the problem.
http://3dartisan.net/chris
obviously it's not done so please ignore the table with the huge photot in it.
http://3dartisan.net/chris
obviously it's not done so please ignore the table with the huge photot in it.
- BUBBALOU
- DBB Benefactor
- Posts: 4198
- Joined: Tue Aug 24, 1999 2:01 am
- Location: Dallas Texas USA
- Contact:
I have both IE and FF, the page is just big blank screen with a title, no menus of any sort in either browser
um
<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
<center><a href=\"Main.html\"><img src=\"Images/Logo.gif\" border = off></a></center>
um
<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
<center><a href=\"Main.html\"><img src=\"Images/Logo.gif\" border = off></a></center>
I seem to have a better workout dodging your stupidity than attempting to grasp the weight of your intelligence.
The XHTML Validator found a ton of problems with your code.
In XHTML, all elements are lowercase. There is no <A> tag, there is no <SPAN> tag. There are, however, <a> and <span>.
It seems you're trying to use litUp1 (a CSS class) as an attribute. You want to do <span class=\"litUp1\"> instead of just <span litUp1>.
IFRAMEs don't exist outside of the IE world, which probably partially explains why FF is freaking out with yours.
In XHTML, all elements are lowercase. There is no <A> tag, there is no <SPAN> tag. There are, however, <a> and <span>.
It seems you're trying to use litUp1 (a CSS class) as an attribute. You want to do <span class=\"litUp1\"> instead of just <span litUp1>.
IFRAMEs don't exist outside of the IE world, which probably partially explains why FF is freaking out with yours.
Thanks.
What is wrong with using iframes? I tried using normal columns but the menus wouldn't go overtop of the bottom frame. I wanted the menu to be separate so I don't need the code in each and every page and have the page reload with every click.
I fixed the FireFox bug. If I fix the dimentions of the borders on one computer. Everything is aligned properly on that computer... but then I try it on a different computer and the layout changes. It's so weird.
Anyone willing to fix the code for me? I like the design and stuff just want to fix the problems.
Help much appreciated. Thanks.
What is wrong with using iframes? I tried using normal columns but the menus wouldn't go overtop of the bottom frame. I wanted the menu to be separate so I don't need the code in each and every page and have the page reload with every click.
I fixed the FireFox bug. If I fix the dimentions of the borders on one computer. Everything is aligned properly on that computer... but then I try it on a different computer and the layout changes. It's so weird.
Anyone willing to fix the code for me? I like the design and stuff just want to fix the problems.
Help much appreciated. Thanks.
you don't need iframe: the same can be achieved using the overflow css attribute on, say, a div tag.
thats how the silly quoting thing is done on this board.
all of the tags that have been deprciated in HTML4 are ones that css can also do(ie all the visual formating elements)
You also might want to review the CSS box model, as it is quite counter-inuitive, and probably the source of your issues with the menu.
thats how the silly quoting thing is done on this board.
all of the tags that have been deprciated in HTML4 are ones that css can also do(ie all the visual formating elements)
You also might want to review the CSS box model, as it is quite counter-inuitive, and probably the source of your issues with the menu.
http://3dartisan.net/chris/
I think I fixed it but I couldn't try it on another computer.
body {
font-family: arial, helvetica, serif;
FONT-SIZE: 100%;
background: white;
BACKGOUND: url(Images/MenuBG.gif);
padding: 2em;
margin: 0;
}
I changed the FONT-SIZE from 80% to 100%. I think maybe font sizes are different on more then one computer???
Is there a way to lock the font size so you can't change it in IE? cuzz when I change the font size in IE it messes up the page.
hmm about the overflow css thing. I will have to see if I can find a tutorial on it. I'm a newb when it comes to coding.
I think I fixed it but I couldn't try it on another computer.
body {
font-family: arial, helvetica, serif;
FONT-SIZE: 100%;
background: white;
BACKGOUND: url(Images/MenuBG.gif);
padding: 2em;
margin: 0;
}
I changed the FONT-SIZE from 80% to 100%. I think maybe font sizes are different on more then one computer???
Is there a way to lock the font size so you can't change it in IE? cuzz when I change the font size in IE it messes up the page.
hmm about the overflow css thing. I will have to see if I can find a tutorial on it. I'm a newb when it comes to coding.
Quick, before Mobius gets you for that one...
The reason CSS offers different font size methods (em, %, px, pt, etc.) is because most of them can be dynamically resized. The right thing to do would be to design your code so that it renders properly regardless of font size.
The practical thing to do might be to do that, or use \"pt\" or \"px\" as the specifier for font-size (e.g. font-size: 8pt). The browser cannot resize fonts that are specified to be a certain height in points or pixels.
It is perfectly possible to design a layout that works well when resized but is beautiful. But if that would take a substantial re-engineering of your code, then it might make more sense just to go with point or even pixel sizes.
The reason CSS offers different font size methods (em, %, px, pt, etc.) is because most of them can be dynamically resized. The right thing to do would be to design your code so that it renders properly regardless of font size.
The practical thing to do might be to do that, or use \"pt\" or \"px\" as the specifier for font-size (e.g. font-size: 8pt). The browser cannot resize fonts that are specified to be a certain height in points or pixels.
It is perfectly possible to design a layout that works well when resized but is beautiful. But if that would take a substantial re-engineering of your code, then it might make more sense just to go with point or even pixel sizes.
Code: Select all
div { overflow : scroll}
You can specify a font size be so much bigger or smaller than the parent by adding a minus or a plus in front of the value.
eg:
Code: Select all
p { font-size: -3pt}
Thanks! I got the text size to work properly right now.
One thing I notice is that my links don't change colour in FireFox when I have my mouse over them. In IE it works fine. Not a big deal I guess.
This is the code i'm using right now to embedded the other pages within the table.
<IFRAME SRC=\"Pages/Welcome.html\" Width=\"995\" Height=\"590\" FRAMEBORDER=\"0\"></IFRAME>
I can't find any tuts on the overflow command. I have no idea what to even search for. How is it better for compatibility.
Thanks.
One thing I notice is that my links don't change colour in FireFox when I have my mouse over them. In IE it works fine. Not a big deal I guess.
This is the code i'm using right now to embedded the other pages within the table.
<IFRAME SRC=\"Pages/Welcome.html\" Width=\"995\" Height=\"590\" FRAMEBORDER=\"0\"></IFRAME>
I can't find any tuts on the overflow command. I have no idea what to even search for. How is it better for compatibility.
Thanks.
Instead of using an IFRAME, you would use the following:
The downside is that now every one of your pages needs to follow the same \"template\" -- <div> does not behave like <iframe>.
If you knew JavaScript it would be easier to get around this problem (by dynamically changing the content: attribute) but we won't get into that.
Code: Select all
<div style=\"overflow: scroll; width: 995px; height: 590px; border: 0px\">
<!-- page content goes here -->
</div>
If you knew JavaScript it would be easier to get around this problem (by dynamically changing the content: attribute) but we won't get into that.
Or instead of Javascript, you could also handle it server side with server side includes (SSI). Chances are your hosting package allows for these. This way, you still only need to save the menu to one file. But for each of your real pages, you'll need to insert a line of code into your HTML that your server will interpret and include the menu automatically into the code before anyone's browser even gets to see it, so you don't have to worry about whether or not the user's Javascript is existent or borked. That's the advantage. The disadvantage is that the user's browser will still have to redownload the menu code every time he clicks on a page that he hasn't been before. But maintenance-wise, it's just as effective as Javascript and doesn't require the user to have working Javascript.