Apache OpenOffice (AOO) Bugzilla – Issue 6230
Where the second problem *really* happens (under Mozilla)
Last modified: 2004-03-22 16:11:29 UTC
Hi: My fault. Gave the index page where it originally had problems, not the reading pages where the problem currently exists. Here, under Mozilla at least, the CSS accessed by the content overrides the site-wide CSS. As far as the previous cases mentioned (http://es.openoffice.org/abc etc.), I could see why it happened (new page served within iframe/pop-up window, therefore would have templates re-served) but I was looking for a solution. As far as iframes being evil, I know that's how they're seen, but at least as far as my Que XHTML book is concerned (2001), iframes are valid XHTML tags. And they can be very useful. Amazon for example is doing some pretty ingenious things with them as cut and paste tools for Associates' use, and if we used them we could create cut and paste code which would allow us to create communication spaces all over the web (instant updating of new version information in all sorts of places for example). See example below at the tryout site I did way back (this is NOT a commercial site, it's a painting, nothing more!). http://info.wordstop.com/openoffice/recursos/iframesnot.htm
Marked this as a dupplicate of issue 6229. The discussion on the use of the iframe tag is a valid one, but I propose we move that to dev@website.openoffice.org. It is not an issue with SC or the site, but an issue of style. as to the SC generated frames - there is nothing we can do about that (for now, at least). About the CSS, it does override in my broser as well. However, bear in mind that we are defining 2 conflicting CSS statements in one page, and that CSS does not tell the server how to render a page, but your browser how to render it. Again, defining another CSS is fine, but make sure you use unique classes when doing so. *** This issue has been marked as a duplicate of 6229 ***
As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details.
For technical reasons we have to move the issue to another subcomponent tan 'www'. Sorry for bothering you with this generated notification message. There is no need for any action from yor side. Thanks for your understanding, Stefan