Closed Bug 230989 Opened 21 years ago Closed 19 years ago

dynamic writing of frame does NOT set stylesheet

Categories

(Core :: DOM: CSS Object Model, defect)

x86
Windows 98
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: ve3ll, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7a) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7a) Gecko/20040113

When a frame is rewritten and the html in the new frame contains
a pointer to a stylesheet, that stylesheet is not used.  If the
new page has style element it is used correctly! There seems to 
be problem executing the link element !!
NOTE: devzone is setup only to display demo file that exhibits this bug!


Reproducible: Always

Steps to Reproduce:
1.access  home.cogeco.ca/~devzone/
2.press the button in right frame to rewrite the left frame.
3.

Actual Results:  
left frame displays in green, responding to the 
style element rule in the dynamic page!

Expected Results:  
left frame should be in blue if it correctly
responded to the cascaded stylesheet link.

Could this be related to problem that also prevents
displaying the frame source of a dynamically written file???
stylesheet is served as text/plain, so Mozilla correctly decides it's not a CSS
sheet and ignores it. It should be served as text/css.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Summary: dynamic writing of frame does NOT set stylesheet → dynamic writing of frame does NOT set stylesheet
Even on local (no server) version the stylesheet is 
not read either. i had wanted to send a zip file for
testing but noted that some testers objected to that
way as well ... one can download the files from the
website and note that stylesheets are not respected
i will also add a .htaccess to hopefully correct server
bad configuration issue as well .
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
from original sender
i have included an .htaccess file that forces server to 
send correct mimetype for .css files.
 This was tested by verifying the css
thru the w3.org jigsaw css validator which uses mimetype 
correctly instead of extension [as opera/msie do]...
However the problem still exists ... the stylesheet which
sets a blue background is not read and the existing style
element background is used instead...  of course i can 
build my dynamic files to have a style element but this 
leads to maintenence issues which style sheets are meant
to do away with.  Why no workee ... oh yeah netscape 4.7 
does work ok ;-[  ;-[  but not net 6/7, moz or firebird!
Actually, the problem here is that the dynamically created content uses a
relative stylesheet url, and this is resolved relative to the URL of the
content, which is a javascript: url.  So it simply doesn't point at the sheet on
the server.

Setting dep on bug 49312 
Depends on: 49312
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.