How do I keep FrontPage from adding w & ht to my img elements?

[Guest]

Using FrontPage 2003 SP2 and a remote hosting service that supports
FP/Sharepoint services (APlus). My html source is changed on the remote
server; ie, 'width' and 'height' attributes are being added to my img
elements, which produces incorrect results.

How do I prevent this from happening?

 

[Guest]

What does "incorrect results" mean? Have you tried putting in the correct
wisth and height yourself?

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
http://www.spiderwebwoman.com/resources/
Please reply to the newsgroup for the benefit of others

 

[Trevor Lawrence]

What does "incorrect results" mean? Have you tried putting in the correct
wisth and height yourself?

Isn't it true that where height and width not specified they are added by
FrontPage, using the actual dimensions of the image, and that this speeds up
the loading process?

If the OP wants a different height and width, they only need to be
specified, as Kathleen has said.

 

[Rob Giordano \(Crash\)]

i would guess that it would only speed up the process if the size was not
being adjusted by the user.

personally i prefer to pre-size my images to the size required by the design
before importing and using them in fp. except for adjustable spacer
..gifs...but who uses them anymore?





|
| | > What does "incorrect results" mean? Have you tried putting in the
correct
| > wisth and height yourself?
|
| Isn't it true that where height and width not specified they are added by
| FrontPage, using the actual dimensions of the image, and that this speeds
up
| the loading process?
|
| If the OP wants a different height and width, they only need to be
| specified, as Kathleen has said.
| --
| Trevor Lawrence
| Canberra
| Microsoft MVP - FrontPage
| MVP Web Site http://trevorl.mvps.orgdontl they
|
|

 

[Murray]

By not including width/height, you force the browser to determine those
values. The incremental time for a single image would be negligable. For
lots of images on the same page, that could be different. In addition, the
page will shimmy and shake as these images load since the rendering is
delayed for each image until its width/height can be determined.

And, it's ALWAYS best practice to size your graphics properly before placing
them on the page.

 

[Trevor Lawrence]

By not including width/height, you force the browser to determine those
values. The incremental time for a single image would be negligable. For
lots of images on the same page, that could be different. In addition,
the page will shimmy and shake as these images load since the rendering is
delayed for each image until its width/height can be determined.

And, it's ALWAYS best practice to size your graphics properly before
placing them on the page.

Murray, thanks for clarifying my response.

When I reread what I sent I realised that it could have been misconstrued.

I wrote
What I meant was that specifying height and width speeds up the loading
process.

 

[Murray]

What I meant was that specifying height and width speeds up the loading

process.

Yes, it does. Incrementally.