Closed Bug 126865 Opened 23 years ago Closed 23 years ago

Viewing page on Mac Server with CSS in Standard Mode doesn't render the CSS

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: tyler, Assigned: attinasi)

References

(
URL
)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204 BuildID: 2002020406 It seems that an external cascading style sheet is not being parsed by mozilla, when a standard page is loaded from a mac server. Reproducible: Always Steps to Reproduce: 1. Visit each URL: http://ket.oerth.com/test.html http://ket.oerth.com/test2.html http://dagger.nas.net/test.html http://dagger.nas.net/test2.html 2. Note that only one of them is not red. Actual Results: The standards mode file on the mac server has a black "test". Expected Results: All of the "test"s should be in red. The files on each server are identical. The test works as expected with Netscape 4.7 and Internet Explorer 5.0.
The problem is not the server itself. Please read the 0.9.8 release notes (you should always do that before you file a bug) You have a valid Doc-Type in your Html file and mozilla is in the "strict standard mode". The Problem : ------------------------------------------------ C:\a>wget http://ket.oerth.com/test.css --02:58:32-- http://ket.oerth.com/test.css => `test.css' Connecting to ket.oerth.com:80... connected! HTTP request sent, awaiting response... 200 OK Length: 28 [text/html] ----------------------------------------------- You have the wrong mime-type for your CSS File. (It's text/html but should be text/css) change your mime-type or as workaround remove the doc-type... marking invalid - please reopen if that are not your test files. (we will write an email to the webmaster...)
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Thanks, apparently I missed that section at the bottom of the release notes, however, that doesn't completely resolve this. Even with that note, I'm not sure this the correct functionality. It says "strict" DTD rather than "standard" mode. Should it be doing this with a "loose" DTD? If so the release notes should be changed to say "standard" mode rather than "strict" DTD. If not this may still be a bug, because I'm not using a strict DTD: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
The release note is referring to the mode (the internal mode that you can see in the new Page Info in coming 0.9.9 or a current nightly), not to the actual DTD -- there are some transitional DTDs that trigger standards mode.
You need to log in before you can comment on or make changes to this bug.