Margins - CSS screwy

  • Thread starter Thread starter FuseNews
  • Start date Start date
Yep.
On the include header_home_page delete this: <p align="center">
where it appears here:
<td class="headerlogo" width="150" rowspan="5">
<p align="center">
<img border="0" src="../images/logos

It's an empty paragraph or <p> tag with no closing </p> tag.

Bet that fixes it.

;-)

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
Re: Margins - CSS screwyYep. definite lack of coffee, had the pages and links reversed in my head.

My apologies Jens.

;-)

I think I found FuseNews's problem though


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

In both cases they are looking for the css in the z_site_nav folder where it is.
You claimed that it would be necessary to have it in two places as written. Hence the remark about
lack of Coffee.
The only way for both of them to be correct would be to have
a copy of the .css file in two locations.
Click to expand...
Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.
-----Original Message-----
From: Steve Easton [mailto:[email protected]]
Posted At: 9. maj 2005 13:40
Posted To: microsoft.public.frontpage.client
Conversation: Margins - CSS screwy
Subject: Re: Margins - CSS screwy


Nope.
If you are viewing a page contained in the z_site_nav folder,
to use the css file in the root the path should be <link
rel="stylesheet" type="text/css" href="../atvsource.css">

z_site_nav/atvsource.css is forcing the browser to look for
it in z_site_nav That's why I asked if there's a copy there.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
.......................with a computer

Jens Peter Karlsen said:
Reread your original answer.
In the first case:

http://www.atvsource.com/z_site_nav/header_home_page.htm

You already are in the z_site_nav folder so the relative link
correctly looks like this:

atvsource.css">

In the other case you are in the root web so here the relative link
looks like this:

<link rel="stylesheet" type="text/css"
href="z_site_nav/atvsource.css">

So both links point to the same file.

Forgot to have your coffee this morning?:-)

Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.
Click to expand...
Click to expand...
 
Fixed the missing </p> tag in two places. Still get the same space at the
top.

This has got me very puzzled. We've totally removed the CSS file, and the
space goes away. Put the CSS file back and the space returns.

Any other good ideas?
 
That is because of how it works with Webs locally. Especially diskbased
Webs.
By default it stores diskbased Webs in C:\Documents and
Settings\username\My documents\My Webs
If you use a / in a link there it will cause the browser to look in C:\
for the file. so FP can't support this type of link and instead use a
multitude of ../../../ depending on how far down in the folder hierarchy
you are.

Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.
-----Original Message-----
From: Thomas A. Rowe [mailto:[email protected]]
Posted At: 9. maj 2005 22:08
Posted To: microsoft.public.frontpage.client
Conversation: Margins - CSS screwy
Subject: Re: Margins - CSS screwy


FP doesn't support the single / for going to the root.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage) WebMaster
Resources(tm) FrontPage
Resources, WebCircle, MS KB Quick Links, etc.
==============================================
If you feel your current issue is a results of installing a
Service Pack or security update, please contact Microsoft
Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a security
update, then there is usually no charge for the call.
==============================================

Jens Peter Karlsen said:
Only if you are at the root or 1 level from the root.
../ means go up one level
/ always means the root level no matter how deep you are in the folder
structure.

There are two other possibilities:

./ means current folder
.../ means go up two levels.

Do NOT use the latter! Not all OS's supports it.
-----Original Message-----
From: Steve Easton [mailto:[email protected]] Posted At: 9. maj
2005 15:43 Posted To: microsoft.public.frontpage.client
Conversation: Margins - CSS screwy
Subject: Re: Margins - CSS screwy


The ../ forces the browser to look in the root.
Even if the page being viewed is in a folder at the root level, if
the link to the css is simply <link rel="stylesheet" type="text/css"
href="atvsource.css"> then the browser looks in the containing folder
and not the web root.

If the link is <link rel="stylesheet" type="text/css"
href="z_site_nav/atvsource.css"> it also tells the browser to look in
the z_site_nav folder and not the root

../ switches it to the root.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed..................
..............................with a computer "Murray"
Only if the root is one level above, no?

--
Murray
============

Nope.
If you are viewing a page contained in the z_site_nav
folder, to use
the css file in the root the path should be <link
rel="stylesheet"
type="text/css"
href="../atvsource.css">

z_site_nav/atvsource.css is forcing the browser to look for it in
z_site_nav That's why I asked if there's a copy there.
Click to expand...
Click to expand...
Click to expand...
 
It also allows you to work within subwebs/subsite without ending up with link to the rootweb, etc.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

Jens Peter Karlsen said:
That is because of how it works with Webs locally. Especially diskbased
Webs.
By default it stores diskbased Webs in C:\Documents and
Settings\username\My documents\My Webs
If you use a / in a link there it will cause the browser to look in C:\
for the file. so FP can't support this type of link and instead use a
multitude of ../../../ depending on how far down in the folder hierarchy
you are.

Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.
-----Original Message-----
From: Thomas A. Rowe [mailto:[email protected]]
Posted At: 9. maj 2005 22:08
Posted To: microsoft.public.frontpage.client
Conversation: Margins - CSS screwy
Subject: Re: Margins - CSS screwy


FP doesn't support the single / for going to the root.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage) WebMaster
Resources(tm) FrontPage
Resources, WebCircle, MS KB Quick Links, etc.
==============================================
If you feel your current issue is a results of installing a
Service Pack or security update, please contact Microsoft
Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a security
update, then there is usually no charge for the call.
==============================================

Jens Peter Karlsen said:
Only if you are at the root or 1 level from the root.
../ means go up one level
/ always means the root level no matter how deep you are in the folder
structure.

There are two other possibilities:

./ means current folder
.../ means go up two levels.

Do NOT use the latter! Not all OS's supports it.

-----Original Message-----
From: Steve Easton [mailto:[email protected]] Posted At: 9. maj
2005 15:43 Posted To: microsoft.public.frontpage.client
Conversation: Margins - CSS screwy
Subject: Re: Margins - CSS screwy


The ../ forces the browser to look in the root.
Even if the page being viewed is in a folder at the root level, if
the link to the css is simply <link rel="stylesheet" type="text/css"
href="atvsource.css"> then the browser looks in the containing folder
and not the web root.

If the link is <link rel="stylesheet" type="text/css"
href="z_site_nav/atvsource.css"> it also tells the browser to look in
the z_site_nav folder and not the root

../ switches it to the root.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed..................
..............................with a computer "Murray"
Only if the root is one level above, no?

--
Murray
============

Nope.
If you are viewing a page contained in the z_site_nav
folder, to use
the css file in the root the path should be <link
rel="stylesheet"
type="text/css"
href="../atvsource.css">

z_site_nav/atvsource.css is forcing the browser to look for it in
z_site_nav That's why I asked if there's a copy there.
Click to expand...
Click to expand...
Click to expand...
 
Since the space goes away when you remove the css file, we have a clue. Because there is
definitely an invisible "return"
at the top of the page. I can even highlight it and copy it to notepad when it creates a
new line, but it is still "invisible" even in notepad. It will show in notepad however,
when highlighted.????

I just looked at the css file and the only thing I can see that I "think" might be causing
it is this, that might be applying
the style twice. ( it shouldn't, but you never know )

..headercontactlinks {font-weight: bold; font-size: 11px; color: #000000; padding: 0px 5px
2px 0px; text-align: right; vertical-align: middle;}
td.headercontactlinks a:hover {text-decoration: underline;}

try changing it to this:

td.headercontactlinks {font-weight: bold; font-size: 11px; color: #000000; padding: 0px
5px 2px 0px; text-align: right; vertical-align: middle;}
td.headercontactlinks a:hover {text-decoration: underline;}

Like I said, this is a guess.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed..................
...............................with a computer
 
That's not the problem. We use TopStyle Pro 3 for our CSS and when we
validate it, it validates OK.. so this cannot be the problem.

Guess we'll have to play with it more to see if we can track it down.
 
Ta da, I found it.

On the page http://www.atvsource.com/z_site_nav/header_home_page.htm
There is a lonely little "un-needed" break tag in the wrong place around line 68 just before the
closing </table> tag:
</tr>
<br>
</table>

remove it like so

</tr>
</table>

and the problem disappears.

Actually I ran the page in CSE HTML validator and it found it.

;-)

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
It became a "quest."

;-)

Glad to help.
Apologies for the bum info about the path to the .css file.
I always make it a habit to keep it in the root.

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
Back
Top