The * is not going to cause a problem such as you describe. You’ll have to show us your <link> tag in the HTML.
Remember that the HTML page is calling the file relative to where it is.
So, assuming a Linux system (don’t ask me about windows):
if they are siblings like this (in the same folder), they are referenced as so:
<link type=“text/css” href=“css.css” rel=“stylesheet”>
so, definitely not with a leading slash (I’ll not get into stuff like mod_rewrite which could change that sort of thing).
If it’s in some whole other folder:
you reference it as
Another note: some characters, such as a BOM (Byte Order Mark) are not always visible while still being able to cause problems. When you save your CSS document, your editor you use, it’s saving it as a regular charset? (iso-8859-1, utf-8, etc and not “unicode”)?
BTW you can reduce redundancy in your code:
padding: 0;<--- most elements do not have default padding, and this can be bad for forms
text-align: left;<-- in a left-to-right page, this is the default
border-width: 0px;<-- the body does not default to a border
padding: 0px;<-- you already did this with the * above
margin: 0px;<-- you already did this with the * above
re forms: removing padding from form elements can make things like submit buttons and select dropdowns more difficult for some users, esp when some browsers (such as Opera) will not let you add the padding back in.
For that reason, many developers only remove padding on elements who have padding and want it gone. Most of the time, for most people, this means lists (ul, ol) because some browsers use margin and others padding to indent lists to make room for bullets.