Zen programmers plz help!!!!!

[gjh42]

It looks like you are entering descriptions in plaintext, inserting format tags where absolutely necessary, and she is using a text editor which puts HTML tags everywhere. Is this the case?

[jill8026]

OMG Kuroi if you lived closer I would kiss you!!!!!!!!!!!!! How did you figure that out?!?!?! I guess I will just create a div for that text.....but the strange thing is the site has been fine with it in there for the last few weeks....why would it all of a sudden do that when editing pages....not sure how that all plays a part......

Either way THANK YOU, you are my hero!!!

[fairestcape]

Which wysiwyg editor is she using?

It may also be that she is happily formatting the page in this editor (which accounts for the additional font descriptions, etc).

Less sophisticated editors (such as freebee editors) still use html tags to format elements, rather than using css.

[gjh42]

You appear not to be using <p> tags for your descriptions, while your client's editor puts them everywhere.

The #mainWrapper p {} targets all <p> tags inside the mainWrapper - i.e. every one on your site. If you want to format paragraphs in descriptions, use a rule like

#productDescription p {width:550px; margin: 1.0em 0.5em;}

or whatever specifics you actually want. The
margin-top: -130px; margin-left:50px;
would cause havoc if generally applied; it looks tailored for a very specific location.

[kuroi]

OMG Kuroi if you lived closer I would kiss you!!!!!!!!!!!!! How did you figure that out?!?!?! I guess I will just create a div for that text.....but the strange thing is the site has been fine with it in there for the last few weeks....why would it all of a sudden do that when editing pages....not sure how that all plays a part......

Either way THANK YOU, you are my hero!!!

LOL. Watch what you say. I'll be flying past you on Friday ... might just ask if they've got a spare parachute on board.

Not sure that creating another div would be a good idea. Other posters are right that there some problems with matching opening and closing div tags.

Finding it was just a matter of reading the clues. The difference between the descriptions entered by you and your client were the p and font tags. When you switched to classic (often a useful diagnostic move) the problem went away. So it had to be an interaction between those tags and how the template was handling them, ergo the stylesheet.

Lesson: Good things come to those who tweet.

[jill8026]

I appreciate everyones help!

Kuroi where you coming to that you will be out this way? Must be something good so I want to be sure I am not missing anything!!!!

And why would these div issues not show up in Dreamweaver when I do a validation...I am not seeing them anywhere...

I had to get that text to lie underneath the image so what other option would there be to do...I have it as a DIV now and all seems to be well in all the browsers I just tested..

I know I still have to finish validation on the site....but I did a quick validation about 2 weeks ago to find any big issues and nothing major like DIV tags ever came up!

Maybe I am validating wrong?!?!?!