![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Beauregard T. Shagnasty wrote: AJBopp wrote: Ok, I'm a newbie but this is too weird for words. Why does http://www.wesleyumc-vinton.org/beta/index.html not render correctly in FF, but Error: The style sheet http://www.wesleyumc-vinton.org/beta/style1.css was not loaded because its MIME type, "application/octet-stream", is not "text/css". http://www.wesleyumc-vinton.org/index.html renders OK? Especially since the CSS in the second case is really crappy and full of errors? (my first effort at it). http://jigsaw.w3.org/css-validator/v...org/index.html You need to remove the style type="text/css" from that style sheet. Use the Web Developer's Toolbar with Firefox, and you can find things like this in .. double-quick time. http://chrispederick.com/work/webdeveloper/ I have the web develepers toolbar and I use it all the time. Its really handy. When I look at AJBopp's site in FF, it doesn't load the css. But when I click on "edit css" it loads fine. I can then see the contents of the page as well as the css in the editor. However, when I try to look at the style sheet in firefox, it thinks its an application and tries to download it, instead of simply viewing it, obviously because the mime type is wrong. But what I would like to know is how do you get the error that tells you the mime type is application/octet-stream ? Inquiring minds want to know ! |
#12
| |||
| |||
|
|
Once upon a time *meltedown* wrote: However, when I try to look at the style sheet in firefox, it thinks its an application and tries to download it, instead of simply viewing it, obviously because the mime type is wrong. But what I would like to know is how do you get the error that tells you the mime type is application/octet-stream ? |
|
Inquiring minds want to know ! |
|
I can see it the Javascript Console: --------- Error: The stylesheet http://www.wesleyumc-vinton.org/beta/style1.css was not loaded because its MIME type, "application/octet-stream", is not "text/css". --------- |
#13
| |||
| |||
|
|
Once upon a time *meltedown* wrote: Beauregard T. Shagnasty wrote: AJBopp wrote: Ok, I'm a newbie but this is too weird for words. Why does http://www.wesleyumc-vinton.org/beta/index.html not render correctly in FF, but Error: The style sheet http://www.wesleyumc-vinton.org/beta/style1.css was not loaded because its MIME type, "application/octet-stream", is not "text/css". http://www.wesleyumc-vinton.org/index.html renders OK? Especially since the CSS in the second case is really crappy and full of errors? (my first effort at it). http://jigsaw.w3.org/css-validator/v...org/index.html You need to remove the style type="text/css" from that style sheet. Use the Web Developer's Toolbar with Firefox, and you can find things like this in .. double-quick time. http://chrispederick.com/work/webdeveloper/ I have the web develepers toolbar and I use it all the time. Its really handy. When I look at AJBopp's site in FF, it doesn't load the css. But when I click on "edit css" it loads fine. I can then see the contents of the page as well as the css in the editor. However, when I try to look at the style sheet in firefox, it thinks its an application and tries to download it, instead of simply viewing it, obviously because the mime type is wrong. But what I would like to know is how do you get the error that tells you the mime type is application/octet-stream ? Inquiring minds want to know ! I can see it the Javascript Console: --------- Error: The stylesheet http://www.wesleyumc-vinton.org/beta/style1.css was not loaded because its MIME type, "application/octet-stream", is not "text/css". --------- Ok, now I see it. It's there but it doesn't light up the little red |
#14
| |||
| |||
|
|
Darin McGrew wrote: AJBopp wrote: Thanks! That eliminates one problem. Now if I could just get teh CSS to render in Firefox! ![]() meltedown <groups2 (AT) reenie (DOT) org> wrote: It must be something to do with your server. Here's the same page on my server and it works fine in Firefox http://www.reenie.org/test/test3/ Yep. The file http://www.wesleyumc-vinton.org/beta/style1.css is being sent as application/octet-stream rather than as text/css. How do you know ? Is there some way of telling what its being sent as ? |
#15
| |||
| |||
|
|
meltedown wrote: Darin McGrew wrote: AJBopp wrote: Thanks! That eliminates one problem. Now if I could just get teh CSS to render in Firefox! ![]() meltedown <groups2 (AT) reenie (DOT) org> wrote: It must be something to do with your server. Here's the same page on my server and it works fine in Firefox http://www.reenie.org/test/test3/ Yep. The file http://www.wesleyumc-vinton.org/beta/style1.css is being sent as application/octet-stream rather than as text/css. How do you know ? Is there some way of telling what its being sent as ? In Mozilla Suite CTRL+I getst the page info display. In Firefox right-click and choose page info. As far as I know there is no analog in Internet Explorer. Yes but... If a stylesheet is being sent as an application/octet-stream, |
#16
| |||
| |||
|
|
Arne wrote: I can see it the Javascript Console: --------- Error: The stylesheet http://www.wesleyumc-vinton.org/beta/style1.css was not loaded because its MIME type, "application/octet-stream", is not "text/css". --------- Precisely where I saw it, Arne. |
#17
| |||
| |||
|
|
Ed Mullen wrote: meltedown wrote: Darin McGrew wrote: AJBopp wrote: Now if I could just get teh CSS to render in Firefox! ![]() meltedown <groups2 (AT) reenie (DOT) org> wrote: It must be something to do with your server. Here's the same page on my server and it works fine in Firefox http://www.reenie.org/test/test3/ Yep. The file http://www.wesleyumc-vinton.org/beta/style1.css is being sent as application/octet-stream rather than as text/css. If a stylesheet is being sent as an application/octet-stream, I can't open it in firefox. Can you ? So therefore I can't look at the page info. |
#18
| |||
| |||
|
|
Once upon a time *Beauregard T. Shagnasty* wrote: Arne wrote: I can see it the Javascript Console: --------- Error: The stylesheet http://www.wesleyumc-vinton.org/beta/style1.css was not loaded because its MIME type, "application/octet-stream", is not "text/css". --------- Precisely where I saw it, Arne. But the strange thing is, when http://www.wesleyumc-vinton.org/beta/index.html gives an error and the css is therefore not loaded, http://www.wesleyumc-vinton.org/index.html gives "only" a warning and loads the css, the MIME type is the same in both cases. -------------- Warning: The stylesheet http://www.wesleyumc-vinton.org/style.css was loaded as CSS even though its MIME type, "application/octet-stream", is not "text/css". -------------- It's not the same css file, but the server and MIME type is the same. So why is one file loaded but not he other? I can see the same differences in behavior with css files where the MIME type is wrongly served as text/plain. Why can't Mozilla be consistent with this? But it is being consistent. When Firefox acts strange and IE seems fine, |
#19
| |||
| |||
|
|
Arne wrote: Once upon a time *Beauregard T. Shagnasty* wrote: Arne wrote: I can see it the Javascript Console: --------- Error: The stylesheet http://www.wesleyumc-vinton.org/beta/style1.css was not loaded because its MIME type, "application/octet-stream", is not "text/css". --------- Precisely where I saw it, Arne. But the strange thing is, when http://www.wesleyumc-vinton.org/beta/index.html gives an error and the css is therefore not loaded, http://www.wesleyumc-vinton.org/index.html gives "only" a warning and loads the css, the MIME type is the same in both cases. -------------- Warning: The stylesheet http://www.wesleyumc-vinton.org/style.css was loaded as CSS even though its MIME type, "application/octet-stream", is not "text/css". -------------- It's not the same css file, but the server and MIME type is the same. So why is one file loaded but not he other? I can see the same differences in behavior with css files where the MIME type is wrongly served as text/plain. Why can't Mozilla be consistent with this? But it is being consistent. When Firefox acts strange and IE seems fine, what is usually happening is that IE is incorrectly compensating for bad code and Firefox is doing exactly what its supposed to be doing. I don't know for sure but I'd say the difference is that the page that doesn't load has a strict doctype and the other has transitional doctype. So FireFox is being less strict on the transitional page and very strict on the strict page, which is exactly what it should be doing, while IE is confusing things by trying to guess what is intended, which basically means it is ignoring the doctype. So its IE that's being inconsitent. |
#20
| |||
| |||
|
|
Darin McGrew wrote: AJBopp wrote: Thanks! That eliminates one problem. Now if I could just get teh CSS to render in Firefox! ![]() meltedown <groups2 (AT) reenie (DOT) org> wrote: It must be something to do with your server. Here's the same page on my server and it works fine in Firefox http://www.reenie.org/test/test3/ Yep. The file http://www.wesleyumc-vinton.org/beta/style1.css is being sent as application/octet-stream rather than as text/css. How do you know ? Is there some way of telling what its being sent as ? |
![]() |
| Thread Tools | |
| Display Modes | |
| |