Mozilla... Netscape Compatible

  • Thread starter Thread starter wstaylor
  • Start date Start date
W

wstaylor

ummmmm.. why does everything I make in FP look like
garbage in both Mozilla(which is netscape) and
Netscape !!!! The iframe doesn't expand to 100%... the
flash content isn't transparent.... the tables aren't
sized correctly....????!!!!! I used GoLive to set up the
tables... then Dreamweaver for inserting the flash
content... and then FP for links, graphics and
iframe... I did it all with FP before and had the same
if not, worse problems... Do I need to stop using
Frontpage? Maybe??? When will frontpage address
compatibility with all browsers???
 
Well lets see.
You started your trip with a Geo, switched to a Buick in the middle and then
threw in a drive in movie, and then finished the trip with a Cadillac.
Now that you don't like the destination it's all the fault of the Cadillac.

Although html is html, browsers are not all the same. It's up to you to create
your pages so that they are compatible with all browsers.
This is *NOT* a shortcoming with FrontPage, or Dreamweaver or Go-live. It's a
matter of not researching what is compatible across all browser types, and /or
telling your web editing program to write html in a Netscape compatible mode.

In FrontPage it's tools Page Options > Compatibility and set the dropdowns for
what you want.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed..................
...............................with a computer
 
You should probably give up DreamWeaver & GoLive also because you hosed up
the parts they created for you too.

Bob Lehmann
 
blah... blah... blah.... thank you !!!
-----Original Message-----
You should probably give up DreamWeaver & GoLive also because you hosed up
the parts they created for you too.

Bob Lehmann




.
Click to expand...
 
What you are seeing has nothing really to do with FrontPage. Mozilla and
Netscape Navigator are not the same. The latest versions of Navigator (6 and
7)are built upon older versions of the Gecko rendering engine, and not even
complete versions at that. Versions from the 4.x series have nothing to do
with Mozilla as the Mozilla browser was a completely new rendering engine.
Most of the problem is design considerations. You have to know exactly how
the rendering engines behave in order to design for them. FP supports some
pretty standard HTML, the problem is how you use it. For example: If you
want a table cell to be a certain size, you may need to put a transparent
spacer image in it so that the table cell stays that size. If you don't the
Navigator rendering engine will often collapse the cell down or expand it
how it sees fit. Part of the problem with the iframe is, although it is set
to 100% is in a table cell which is set ot 70%.

Checking in Navigator 7.1 rendered about the same results as in IE. In this
case I expect you mean that there were issues with earlier versions of
Navigator such as 4.x. In this instance there's nothing FP, Dreamweaver, or
any other tool will do for you as part of the game in cross-browser
development is designing pages specifically for the bugs/faults of the
various rendering engines of the different browsers. You can create pages in
FP that will have no problems in different browser, or degrade in an
expected manner if they are designed for the appropriate browsers in mind.
These design decisions are independent of which tool you use.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
 
So, even though my response expressed the same general theme as the other
responses, you chose only to reply to it with your witty banter.

Is that because it is shorter than the others, and able to compete better
with your attention span?

Bob Lehman
 
Back
Top