G
Guest
Webpages created with FrontPage 2003 do not display properly in Netscape or
Firefox. How can this be corrected?
Firefox. How can this be corrected?
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
S
Steve Easton
What doesn't display properly??
As with any html editing / web creation program you have to learn what does and doesn't work in
different browsers.
--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
As with any html editing / web creation program you have to learn what does and doesn't work in
different browsers.
--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
M
Murray
The bottom line is this: if you know how to use FP to create browser
compliant pages, then your pages will be browser compliant. It's a bit of a
bootstrap, I know, but what is happening is not that FP is writing bad
code - on the contrary, it's doing exactly what you have told it to do (most
likely). The problem is that what you have told it to do is not going to be
browser compliant.
An example or two might help.
1. Put a <marquee> tag on the page. View it in Netscape (not Firefox). It
will not 'marquee'.
2. Use a page transition filter on the page. View it on the Mac. The page
will not transition.
3. Drop some word art on the page. View it in any non-IE browser. The
words will not 'art' so to speak.
Unfortunately, the only way to know these things is to practice with them,
preview often in the various browsers, and get a good HTML book. The better
you understand HTML, the more cross-browser your pages will become.
compliant pages, then your pages will be browser compliant. It's a bit of a
bootstrap, I know, but what is happening is not that FP is writing bad
code - on the contrary, it's doing exactly what you have told it to do (most
likely). The problem is that what you have told it to do is not going to be
browser compliant.
An example or two might help.
1. Put a <marquee> tag on the page. View it in Netscape (not Firefox). It
will not 'marquee'.
2. Use a page transition filter on the page. View it on the Mac. The page
will not transition.
3. Drop some word art on the page. View it in any non-IE browser. The
words will not 'art' so to speak.
Unfortunately, the only way to know these things is to practice with them,
preview often in the various browsers, and get a good HTML book. The better
you understand HTML, the more cross-browser your pages will become.
G
Guest
Murray said:The bottom line is this: if you know how to use FP to create browser
compliant pages, then your pages will be browser compliant. It's a bit of a
bootstrap, I know, but what is happening is not that FP is writing bad
code - on the contrary, it's doing exactly what you have told it to do (most
likely). The problem is that what you have told it to do is not going to be
browser compliant.
An example or two might help.
1. Put a <marquee> tag on the page. View it in Netscape (not Firefox). It
will not 'marquee'.
2. Use a page transition filter on the page. View it on the Mac. The page
will not transition.
3. Drop some word art on the page. View it in any non-IE browser. The
words will not 'art' so to speak.
Unfortunately, the only way to know these things is to practice with them,
preview often in the various browsers, and get a good HTML book. The better
you understand HTML, the more cross-browser your pages will become.
--
Murray
Thanks Murray...
M
Murray
You're welcome. It wasn't much help in the short-term. Perhaps if you post
a link to your page, the combined eyeballs here can find some weak spots for
you!
a link to your page, the combined eyeballs here can find some weak spots for
you!
D
Donald Link
On Tue, 11 Jan 2005 05:07:04 -0800, "bdmilinsky"
Pges created with FrontPage 2003 do not display properly in Netscape
or
Well, since you provided so much "detailed" information I am sure you
will get a million replies. Frontpage 2003 will publish and display
correctly in Firefox. Period. The problem is some other reason.
Does it display ok in explorer?
Pges created with FrontPage 2003 do not display properly in Netscape
or
Firefox. How can this be corrected?
Well, since you provided so much "detailed" information I am sure you
will get a million replies. Frontpage 2003 will publish and display
correctly in Firefox. Period. The problem is some other reason.
Does it display ok in explorer?
G
Guest
Dear Donald:Donald Link said:On Tue, 11 Jan 2005 05:07:04 -0800, "bdmilinsky"
Pges created with FrontPage 2003 do not display properly in Netscape
or
Well, since you provided so much "detailed" information I am sure you
will get a million replies. Frontpage 2003 will publish and display
correctly in Firefox. Period. The problem is some other reason.
Does it display ok in explorer?
Yes, it displays correctly viewed by Internet Explorer. To view the site go
to...
www.e-concierge.com.
Thanks for you help.
T
Thomas A. Rowe
You are using...
1. Absolute Positioning which is not handled well in other browsers.
2. VML graphics (Word Art, Shapes, etc.) which is only supported in IE browsers under Windows.
3. It appears you have used Word to create some content, as well.
4. Inline style tags, not well supported outside of IE
You can keep the same look by using tables to structure your page layout and an external style
sheet. Create images in a graphic application, in place of the WordArt. Create all text directly in
FP or paste into Notepad first, then into FP.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
1. Absolute Positioning which is not handled well in other browsers.
2. VML graphics (Word Art, Shapes, etc.) which is only supported in IE browsers under Windows.
3. It appears you have used Word to create some content, as well.
4. Inline style tags, not well supported outside of IE
You can keep the same look by using tables to structure your page layout and an external style
sheet. Create images in a graphic application, in place of the WordArt. Create all text directly in
FP or paste into Notepad first, then into FP.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
D
Donald Link
Dear Donald:
Yes, it displays correctly viewed by Internet Explorer. To view the site go
to...
www.e-concierge.com.
Thanks for you help.
Your right. In Firefox the frames or tables, or whatever you used, the
text is covered by a background color more than a little. But have
you noticed in Explorer they are also to close to the background image
to the point it looks quite bad. I think it is more of a design
problem than the browser but I am not really smart enough to suggest
why. Have you experimented with centering the text at at greater
distance. I know I use Firefox as my main browser and also use
explorer to check and I find only very minor differences. Usually
the differences are slight difference of displaying text and not much
at all in graphics. It is more of a feeling of difference rather than
a technical difference. Nothing like yours looks. I have a site in
the works for grandparents and am learning more everytime I make a
change. You can see at www.grand3.com if you care to. It just takes
time.
M
Murray
1. Absolute Positioning which is not handled well in other browsers.
That's incorrect.
That's incorrect.
That's incorrect.
4. Inline style tags, not well supported outside of IE
That's incorrect.
T
Thomas A. Rowe
Murray,
I didn't say that don't work, just not handled well, I guess I could of added, the way they are
implemented via FP.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
I didn't say that don't work, just not handled well, I guess I could of added, the way they are
implemented via FP.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
M
Murray
Actually, there is not a problem with FP implements them, either. The
problem is really in how people use them on the page.
A properly built page with absolutely positioned elements correctly used,
containing both inline styled and fully CSS qualified code, will render
indentically in all modern browsers.
problem is really in how people use them on the page.
A properly built page with absolutely positioned elements correctly used,
containing both inline styled and fully CSS qualified code, will render
indentically in all modern browsers.
T
Thomas A. Rowe
I consider NS 4 browsers to still be valid
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
T
Thomas A. Rowe
Users use them on the page by being able to select them, and FP adds them to the page, then the
pages do not display as the users would expect in various browsers and screen resolutions. To me
this has to be the way FP has implemented the functions. A solution would be to have a better dialog
box.
If you know how to work with CSS, then you can manually work around these issues for the various
browsers and resolutions.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
pages do not display as the users would expect in various browsers and screen resolutions. To me
this has to be the way FP has implemented the functions. A solution would be to have a better dialog
box.
If you know how to work with CSS, then you can manually work around these issues for the various
browsers and resolutions.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
M
Murray
And NN4 gets most layer things right.
If you follow the guidelines posted here, NN4x will be fine, too -
http://www.great-web-sights.com/g_layerlaws.asp
If you follow the guidelines posted here, NN4x will be fine, too -
http://www.great-web-sights.com/g_layerlaws.asp
M
Murray
The problem is in how the users are placing them on the page. Putting a
layer into a table cell is probably 90% of the problem. It's not a good
code practice. This has nothing to do with the HTML authoring system, and
everything to do with the experience of the user. I wish there were a way
to alert people that this is a bad idea, but there is not.
layer into a table cell is probably 90% of the problem. It's not a good
code practice. This has nothing to do with the HTML authoring system, and
everything to do with the experience of the user. I wish there were a way
to alert people that this is a bad idea, but there is not.
T
Thomas A. Rowe
FP make it very easy to use features/functions without have knowledge of the feature or function or
the technology behind it.
So when these features/functions are used, they don't work in many cases outside of IE. IE does it
best to try and display the page as would be expected by correcting the developer mistake (when
possible), where as other browsers tend not to attempt to correct errors.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
the technology behind it.
So when these features/functions are used, they don't work in many cases outside of IE. IE does it
best to try and display the page as would be expected by correcting the developer mistake (when
possible), where as other browsers tend not to attempt to correct errors.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
M
Murray
This is mostly true. But you don't want FP to somehow prevent the user from
doing perfectly valid things either, nor do you want to say that something
that is valid must not be because it is poorly supported. The truth is that
it's not poorly supported.
As with all things that FP allows you to do, you need to understand what to
do a bit to use it correctly....
doing perfectly valid things either, nor do you want to say that something
that is valid must not be because it is poorly supported. The truth is that
it's not poorly supported.
As with all things that FP allows you to do, you need to understand what to
do a bit to use it correctly....
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.