Apache OpenOffice (AOO) Bugzilla – Issue 12295
Style tag in header is missing type attribute
Last modified: 2013-08-07 14:38:26 UTC
(The file attached to 12294 was used to generate this error) The style tag within the head tags is missing the required type attribute. While 3.2 did not require a type attribute, it also states that style is a "...place holder for the introduction of style sheets..." and "user agents should hide the contents of these elements." Since the only version of HTML that recognizes the style element is 4.0, the 4.0 guidelines should be followed.
Still occurs in OO v1.1b, even when the DTD specified by OO is for HTML 4.0.
Rick, thank you for this information. Verified RH 9.0, 1.1 Beta 2. <STYLE> tag inside the <HEAD> element does not have the TYPE attribute as specified in http://www.w3.org/TR/html401/present/styles.html#edef-STYLE
Created attachment 7166 [details] Test Word doc for HTML export
.
Just curios, why the push to 2.0? This seems like a simple fix for 1.1.
Reassigned to ES
Reassigned to MIB
Since all user agents use CSS by default, P4 seems to me the correct priority.
Just beware that while the user-agents you have used may have defaulted to text/css, this may not always be the case as the specification doesn't define a default. http://www.w3.org/TR/html401/present/styles.html#edef-type-STYLE "This attribute specifies the style sheet language of the element's contents and overrides the default style sheet language. The style sheet language is specified as a content type (e.g., "text/css"). Authors must supply a value for this attribute; there is no default value for this attribute."
According to the OpenOffice.org roadmap (http://tools.openoffice.org/releases) this issue was retargeted to OOo Later.
This bug still exists in OO 2.0.4. Is it such a fuzz to change this so that it saves a HTML file like this: <STYLE TYPE="TEXT/CSS"> Please fix this simple bug.
This bug seems to be fixed in OO 2.2.1. When generating HTML output, this output now is W3C valid (the <STYLE TYPE="TEXT/CSS"> has been added). Please set this bug to RESOLVED.