XHTML file ignores stylesheet



15 years ago
14 years ago


(Reporter: paul, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

I have a simple XHTML file:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
	<link rel="stylesheet" type="text/css" media="screen" href="shortform.css"/>
<p>This should be white on black</p>

And a simple style sheet:
	background-color: #000000;
	color: #E0E0E0;

The stylesheet is ignored if I pull the page from a WSAD 5.1 Java App server
using Mozilla 1.6 beta or Firebird 0.4.

The stylesheet is used if I point the browser to a copy on the disk.

The stylesheet is used if I delete the doc-type line in the HTML file.

By doing a packet trace, I confirmed that even when the stylesheet is not used,
Mozilla does pull it across the network.

I do not have problems with this when the file is served up by tomcat instead of
WSAD 5.1.

IE 5.5 does not have problems with either server.

Reproducible: Always

Steps to Reproduce:
See above.
Actual Results:  
Page is displayed with default style information.

Expected Results:  
Use the stylesheet.

Comment 1

15 years ago
This occurs with the WebSphere 4.0 test environment. It does not occur when the
page is served up by the WebSphere 5.0 test environment.

Comment 3

15 years ago
Are you certain it's being served with the right MIME type? I believe the
Javascript Console (Tools -> Web Development -> Javascript Console) shows errors
about that...
see comment 3. please reopen if this bug occurs when the server sends the
correct mime type.
Last Resolved: 15 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey

Comment 5

14 years ago
Make that bug 228922 instead.

Comment 6

14 years ago
Ignore the above comment that got here. Wrong bug...
You need to log in before you can comment on or make changes to this bug.