frontpage 2003 changes my html when publishing

[Guest]

I use TopSyle Pro in connection with Frontpage, so as to insure that we meet
W3C standards, and more so for cross browser functionality.

I just noticed that when I publish our pages using frongpage 2003 (web
server publishing) that it is adding code to the remote site pages. For
example, if I have an image placed and defined by CSS and no width or height
in the source code, Frontpage will then add this to the page published on the
remote site. This in effect invalidates or W3C compliance because of the doc
type we have.

I have optimized published disabled, but don't see anywhere where I can stop
this change. Is there a method to disable this?

If I switch to FTP publishing will that interfer with the Ecommerce add in
pages? I don't use any other the frontpage features with exception to the
include component.

 

[Guest]

FrontPage adds height= and width= attributes to <img> tags because that way,
the browser can reserve space for the picture and continue formatting the
rest of the page. Otherwise, the browser has to wait for the picture to
arrive before it can display subsequent content.

This is really a valuable feature. I suggest not degrading your site in
order to make some validator program happy.

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*-----------------------------­-----------------------
|\----------------------------­-----------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||----------------------------­-----------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/----------------------------­-----------------------
*-----------------------------­-----------------------

 

[Cheryl D Wise]

JT,

I also use TopStyle Pro and am very concerned about cross browser and cross
platform functionality as well as web accessibility.

Like Jim I suggest leaving the height and width in the image's html. There
are several reasons for this.

First, as Jim mentioned it speeds up the page layout since the browser can
reserve space and move on. Height and width are part of the content's
properties and not presentational unless you are using height and width to
resize images. Something not recommended due to distortion and download size
issues.

Height and width in the HTML works even with browser that do not support
CSS. Remember that not everyone uses a web browser on a computer. Many
alternative devices have little or not support for CSS.

Positioning, float, etc. those are all values that work well in CSS but
basic image are fine but if you put the height and width of every image in
your stylesheet you will need a lot of IDs or classes which will bloat your
stylesheet. Especially since most of the images will be used only on one
page within your site.

As to whether switching to FTP will interfere with your eCommerce add-in,
look at the documentation for or the site of your add-in creator.

--
Cheryl D. Wise
MS FrontPage MVP
http://mvp.wiserways.com
http://starttoweb.com
Online instructor led web design training - Next Session June 26th