I see applications where informations that are provided in the (X)HTML head are needed at other places of the body. But they can be dropped or cut off by an import or transformation procedure.
- CMS
http://en.wikipedia.org/wiki/Content_management_system
- Portals
http://en.wikipedia.org/wiki/Portlet
So I suggest that your library can be used to restore those values.
Possibilities:
1. See request "convert HTML head information into javascript code inside the body".
http://groups.google.de/groups?threadm=40ed1d8f.0301251340.51db2f5f%40posting.google.com
2. Move element "style" into the corresponding attribute of the element "div".
This solution will work if the specification 'Syntax of CSS rules in HTML's "style" attribute' will become a recommendation and the browsers/user agents will support this evolving standard.
http://www.w3.org/TR/css-style-attr
How do you think about such ideas?
A German discussion on the topic "Stileinstellungen verlagern" was also started.
http://groups.google.de/groups?threadm=40ed1d8f.0403030137.2ef908e2%40posting.google.com
Logged In: YES
user_id=605407
Are you only worried about the STYLE tag in the HEAD?
1) It's not clear to me that script could replace style.
2) This might be more straight-forward. Wouldn't the style
in the HEAD apply to everything in the BODY rather than a
DIV. In other words, wouldn't you move the style from the
STYLE tag in the HEAD to the style attribute in the BODY
(creating one if there wasn't one of course)?
Logged In: YES
user_id=572001
1) Yes. Did you try to use the document object model?
The script can set style properties. I assume that it will be hard to move meta tags to other places of the source code.
Script commands should be used at the moment because the specification is at the state "W3C Working Draft 15 May 2002".
2) - Which user agents support the style attribute for the body element?
- Portlets won't contain a body tag. Do you know what the corresponding element will be for a portal component?