Article ID: 194234 - Last Review: October 3, 2001 - Revision: 1.0 FP98: FrontPage Editor Deletes Unknown Attributes in HTMLThis article was previously published under Q194234 For a Microsoft FrontPage 97 version of this article, see 161420 (http://support.microsoft.com/kb/161420/EN-US/ ) . SYMPTOMS
When the FrontPage Editor parses HTML, there are certain tags for
which unknown attributes are discarded.
CAUSE
FrontPage normalizes HTML to the HTML 2.0 specification (RFC 1866),
or, where the 2.0 specification is superceded, to the HTML 3.2
proposal.
RESOLUTION
If you want to write HTML with unknown attributes to tags identified
in the "More Information" section of this article, put the entire tag
into an HTML Markup section.
To insert an HTML Markup section, follow these steps:
MORE INFORMATION
The FrontPage Editor knows about a certain set of attributes for each HTML
tag it can write. FrontPage Editor preserves these known attributes.
You can manipulate them using dialog boxes and direct manipulation
in the HTML Markup dialog box in FrontPage 98. When the FrontPage Editor
encounters an attribute it does not recognize, it attempts to put that
attribute and its value into the extended attribute list for that tag. Any
tag for which the FrontPage Editor preserves extended attributes will
include an Extended button in its Properties dialog box. The attribute list
is preserved by the FrontPage Editor in its extended attributes list for
that tag and is inserted into the final HTML.
Not all tags have extended attribute lists in FrontPage. The following HTML tags do not have an extended attribute list in FrontPage Editor:
AREA, B, BASE, BASEFONT, BGSOUND, BIG, BLINK, CENTER, CITE, CODE,
DFN, DIV, EM, FONT, HEAD, HTML, MAP, META, NEXTID, NOFRAMES,
OPTION, SAMP, SCRIPT, SMALL, STRIKE, S, STRONG, SUB, SUP, TITLE,
TT, U, VAR, NOEMBED, PARAM.
When you work with these tags, unrecognized attributes are discarded
by the FrontPage Editor.
| Article Translations
|

Back to the top
