In version 5.x, when I inserted an image using 'img' tag in a node, by default the image will take up a separate line over the following texts. Only when I used align="left" property the following would wrap around the image.

Now in version 6, I found by default the following texts always wrap around the image, even though I did not use align=left property.

Can you advise how to make it work as the 5.x version? Thanks.

Comments

huayen’s picture

ANy help? Thanks in advance.

jan’s picture

Got the same problem

huayen’s picture

Still waiting for solution.

huayen’s picture

Due to this problem I have to keep my site offline. ANyone can help solve this? Your help is greatly appreciated.

Lioz’s picture

well image in content have a float:left property.

I suggest you to add an extra class to your image such as

<img src="......" class="nofloat" />

and then change style.css

#primary. singlepage img.nofloat {
float:none;
}
huayen’s picture

Followed you, but it did not work.

huayen’s picture

#primary img {
margin: 0 15px 0px 0;
padding: 4px;
/*float: left;*/
}

Just comment above one line, solved the problem.

bbodenmiller’s picture

Version: 6.x-1.7 » 6.x-1.9
Category: support » bug
Priority: Normal » Critical
Status: Active » Needs review

Can anyone tell me why the CSS file has the image floating left by default?

AntiNSA’s picture

Im dying to get my images inserted with the image field to float and ytou cant make them stop? I need to wrap the body text around the image. I can only get the image above or below the body, not right or left..... and not wrapped at all : (

Im all ears...

christophweber’s picture

I think lioz' decision to default to float: left; for a simple img tag is a good one since it creates good looking results out of the box for simple pages. For Marinelli-2.x he changed it, BTW.
The flip side is: Once people want to do more fancy things they'll have to worry about CSS classes and educate themselves. IMHO it's a fair trade-off.

oadaeh’s picture

Issue summary: View changes
Status: Needs review » Closed (won't fix)

This issue is being closed because it is against a branch for a version of Drupal that is no longer supported.
If you feel that this issue is still valid, feel free to re-open and update it (and any possible patch) to work with the 7.x-4.x branch.
Thank you.