C
Chris
Are shared borders in FP 2002 or 2003 w3c compliant? If
not what browsers or platform will it not work on?
not what browsers or platform will it not work on?
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
Stefan B Rusynko
Shared borders and Include Pages are design time tools w/ the content (inside the <BODY> tags) of the Shared Border or Include page
"embedded" or included as html in your pages when you save any of the file(s) using them (or save the borders / include pages
themselves)
- you actually don't need them in a live web (unless you are going to edit the site online in FP)
The content you create can be compliant, but most validators will flag the meta tag as unknown
FYI
FP converts your page(s) to a series of tables to include the Shared borders, (which are really just a special case of Include
pages), but FP can not build those tables if either your shared border page content or main page content has illegal html or broken
tag pairs
- usually due to missing </body></html> tags, or unmatched table / cell tags (unclosed table / cell tags), or some other unclosed
html block element
If you can see them using File Preview in Browser they will publish in as part of your pages
If you can't see them using File Preview in Browser, it's because FP can not build the included content tables, so you need to
validate and correct your broken html
| Are shared borders in FP 2002 or 2003 w3c compliant? If
| not what browsers or platform will it not work on?
|
"embedded" or included as html in your pages when you save any of the file(s) using them (or save the borders / include pages
themselves)
- you actually don't need them in a live web (unless you are going to edit the site online in FP)
The content you create can be compliant, but most validators will flag the meta tag as unknown
FYI
FP converts your page(s) to a series of tables to include the Shared borders, (which are really just a special case of Include
pages), but FP can not build those tables if either your shared border page content or main page content has illegal html or broken
tag pairs
- usually due to missing </body></html> tags, or unmatched table / cell tags (unclosed table / cell tags), or some other unclosed
html block element
If you can see them using File Preview in Browser they will publish in as part of your pages
If you can't see them using File Preview in Browser, it's because FP can not build the included content tables, so you need to
validate and correct your broken html
| Are shared borders in FP 2002 or 2003 w3c compliant? If
| not what browsers or platform will it not work on?
|
G
Guest
I'm trying to use the shared borders as a method of
updating nav and footers across hundreds of screens. Is
the shared borders concept a good idea here or should I
look at a Coldfusion template (I have limited CF
experience but I can make it go). The shared borders
concept is easier for me...unless it does not work across
browsers/platforms.
include pages
of Include
illegal html or broken
or some other unclosed
you need to
updating nav and footers across hundreds of screens. Is
the shared borders concept a good idea here or should I
look at a Coldfusion template (I have limited CF
experience but I can make it go). The shared borders
concept is easier for me...unless it does not work across
browsers/platforms.
-----Original Message-----
Shared borders and Include Pages are design time tools w/
save any of the file(s) using them (or save the borders /the content (inside the said:"embedded" or included as html in your pages when you
include pages
are going to edit the site online in FP)themselves)
- you actually don't need them in a live web (unless you
validators will flag the meta tag as unknownThe content you create can be compliant, but most
the Shared borders, (which are really just a special caseFYI
FP converts your page(s) to a series of tables to include
of Include
shared border page content or main page content haspages), but FP can not build those tables if either your
illegal html or broken
unmatched table / cell tags (unclosed table / cell tags),tag pairs
- usually due to missing </body></html> tags, or
or some other unclosed
will publish in as part of your pageshtml block element
If you can see them using File Preview in Browser they
because FP can not build the included content tables, soIf you can't see them using File Preview in Browser, it's
you need to
message news:[email protected]...
S
Stefan B Rusynko
IMHO shared borders are easier (it's plain html) since they are design time tools,
but you will have to publish all pages affected
- they are not runtime like server side includes
|
| I'm trying to use the shared borders as a method of
| updating nav and footers across hundreds of screens. Is
| the shared borders concept a good idea here or should I
| look at a Coldfusion template (I have limited CF
| experience but I can make it go). The shared borders
| concept is easier for me...unless it does not work across
| browsers/platforms.
|
| >-----Original Message-----
| >Shared borders and Include Pages are design time tools w/
| the content (inside the <BODY> tags) of the Shared Border
| or Include page
| >"embedded" or included as html in your pages when you
| save any of the file(s) using them (or save the borders /
| include pages
| >themselves)
| >- you actually don't need them in a live web (unless you
| are going to edit the site online in FP)
| >
| >The content you create can be compliant, but most
| validators will flag the meta tag as unknown
| >
| >FYI
| >FP converts your page(s) to a series of tables to include
| the Shared borders, (which are really just a special case
| of Include
| >pages), but FP can not build those tables if either your
| shared border page content or main page content has
| illegal html or broken
| >tag pairs
| >- usually due to missing </body></html> tags, or
| unmatched table / cell tags (unclosed table / cell tags),
| or some other unclosed
| >html block element
| >
| >If you can see them using File Preview in Browser they
| will publish in as part of your pages
| >
| >If you can't see them using File Preview in Browser, it's
| because FP can not build the included content tables, so
| you need to
| >validate and correct your broken html
| >
| >
| >--
| >
| >_____________________________________________
| >SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| >"Warning - Using the F1 Key will not break anything!" (-;
| >To find the best Newsgroup for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| >_____________________________________________
| >
| >
| message | >| Are shared borders in FP 2002 or 2003 w3c compliant? If
| >| not what browsers or platform will it not work on?
| >|
| >
| >
| >.
| >
but you will have to publish all pages affected
- they are not runtime like server side includes
|
| I'm trying to use the shared borders as a method of
| updating nav and footers across hundreds of screens. Is
| the shared borders concept a good idea here or should I
| look at a Coldfusion template (I have limited CF
| experience but I can make it go). The shared borders
| concept is easier for me...unless it does not work across
| browsers/platforms.
|
| >-----Original Message-----
| >Shared borders and Include Pages are design time tools w/
| the content (inside the <BODY> tags) of the Shared Border
| or Include page
| >"embedded" or included as html in your pages when you
| save any of the file(s) using them (or save the borders /
| include pages
| >themselves)
| >- you actually don't need them in a live web (unless you
| are going to edit the site online in FP)
| >
| >The content you create can be compliant, but most
| validators will flag the meta tag as unknown
| >
| >FYI
| >FP converts your page(s) to a series of tables to include
| the Shared borders, (which are really just a special case
| of Include
| >pages), but FP can not build those tables if either your
| shared border page content or main page content has
| illegal html or broken
| >tag pairs
| >- usually due to missing </body></html> tags, or
| unmatched table / cell tags (unclosed table / cell tags),
| or some other unclosed
| >html block element
| >
| >If you can see them using File Preview in Browser they
| will publish in as part of your pages
| >
| >If you can't see them using File Preview in Browser, it's
| because FP can not build the included content tables, so
| you need to
| >validate and correct your broken html
| >
| >
| >--
| >
| >_____________________________________________
| >SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| >"Warning - Using the F1 Key will not break anything!" (-;
| >To find the best Newsgroup for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| >_____________________________________________
| >
| >
| message | >| Are shared borders in FP 2002 or 2003 w3c compliant? If
| >| not what browsers or platform will it not work on?
| >|
| >
| >
| >.
| >