469,310 Members | 2,439 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,310 developers. It's quick & easy.

Firefox

I have an html file, checked css syntax online
(http://jigsaw.w3.org/css-validator/v...or-uri.html.en)

it all checks fine, got no errors or warnings.. however Firefox is not
reading stylesheet, for some reason.. two examples of errors I get in JS
console:

Error: Unexpected end of file while searching for
closing } of invalid rule set.

Error: Unexpected end of file while searching
for ',' or '{'. Ruleset ignored due to bad selector.

I click on error (which is a link to line in file causing error..)
and it just takes me to top of css file..

I have done css for Firefox many times, have never encountered this..
would appreciate some leads.. thank you very much..

Frances

Jan 24 '06 #1
25 8983
Deciding to do something for the good of humanity, Frances
<fd***@yahoo.com> declared in
comp.infosystems.www.authoring.stylesheets:
I have done css for Firefox many times, have never encountered this..
would appreciate some leads..


A URL to the CSS file in question would make it much easier.

--
Mark Parnell
================================================== ===
Att. Google Groups users - this is your last warning:
http://www.safalra.com/special/googlegroupsreply/
Jan 24 '06 #2
Mark Parnell wrote:
Deciding to do something for the good of humanity, Frances
<fd***@yahoo.com> declared in
comp.infosystems.www.authoring.stylesheets:

I have done css for Firefox many times, have never encountered this..
would appreciate some leads..

A URL to the CSS file in question would make it much easier.

thanks... http://www.francesdelrio.com/cc/viewer.css

Jan 24 '06 #3
Els
Frances wrote:
Mark Parnell wrote:
Deciding to do something for the good of humanity, Frances
<fd***@yahoo.com> declared in
comp.infosystems.www.authoring.stylesheets:
I have done css for Firefox many times, have never encountered this..
would appreciate some leads..


A URL to the CSS file in question would make it much easier.


thanks... http://www.francesdelrio.com/cc/viewer.css


And what is the page that should use that stylesheet?
First I was guessing your main page, but that one doesn't even have a
reference to the stylesheet. Then I figured it would be about the page
http://www.francesdelrio.com/cc/, but that one is referencing a
different stylesheet. So.. which page is it that doesn't let Firefox
read the stylesheet?

--
Els http://locusmeus.com/
Sonhos vem. Sonhos vão. O resto é imperfeito.
- Renato Russo -
Now playing: Duran Duran - A View To A Kill
Jan 24 '06 #4
Els wrote:
Frances wrote:

Mark Parnell wrote:
Deciding to do something for the good of humanity, Frances
<fd***@yahoo.com> declared in
comp.infosystems.www.authoring.stylesheets:
I have done css for Firefox many times, have never encountered this..
would appreciate some leads..

A URL to the CSS file in question would make it much easier.


thanks... http://www.francesdelrio.com/cc/viewer.css

And what is the page that should use that stylesheet?
First I was guessing your main page, but that one doesn't even have a
reference to the stylesheet. Then I figured it would be about the page
http://www.francesdelrio.com/cc/, but that one is referencing a
different stylesheet. So.. which page is it that doesn't let Firefox
read the stylesheet?


I can't post code for pg calling stylesheet (this is for work...
doesn't even go in path I posted earlier for stylesheet, I just
stylesheet there yesterday to check css-syntax on line at the w3c
site..), but call to stylesheet is as follows:

<LINK rel="stylesheet" type="text/css" href="viewer.css">
as you can see, nothing fancy, nothing unusual... thank you very much..

Frances

Jan 24 '06 #5
VK

Frances wrote:
I have an html file, checked css syntax online
(http://jigsaw.w3.org/css-validator/v...or-uri.html.en)

it all checks fine, got no errors or warnings.. however Firefox is not
reading stylesheet, for some reason.. two examples of errors I get in JS
console:

Error: Unexpected end of file while searching for
closing } of invalid rule set.

Error: Unexpected end of file while searching
for ',' or '{'. Ruleset ignored due to bad selector.


You're getting the same error for http://www.google.com (check the
console) and this crap started with Firefox 1.5
Some browser bug no one managed to narrow down yet I guess. Seems not
directly related with CSS itself but with redirection/headers from the
server side.

Jan 24 '06 #6
Frances wrote:
Els wrote:
Frances wrote:

Mark Parnell wrote:

Deciding to do something for the good of humanity, Frances
<fd***@yahoo.com> declared in
comp.infosystems.www.authoring.stylesheets:
> I have done css for Firefox many times, have never encountered
> this.. would appreciate some leads..

A URL to the CSS file in question would make it much easier.
thanks... http://www.francesdelrio.com/cc/viewer.css

And what is the page that should use that stylesheet?
First I was guessing your main page, but that one doesn't even have a
reference to the stylesheet. Then I figured it would be about the page
http://www.francesdelrio.com/cc/, but that one is referencing a
different stylesheet. So.. which page is it that doesn't let Firefox
read the stylesheet?


I can't post code for pg calling stylesheet (this is for work... doesn't
even go in path I posted earlier for stylesheet, I just stylesheet there
yesterday to check css-syntax on line at the w3c site..), but call to
stylesheet is as follows:

<LINK rel="stylesheet" type="text/css" href="viewer.css">
as you can see, nothing fancy, nothing unusual... thank you very much..

Frances


Hard to tell without a look at the actual server environment you are
seeing the error on. But, I'd suspect that possibly the server is
sending the wrong MIME type for the style sheet OR, possibly, that the
relative link in the HTML reference is not resolving correctly. Try an
absolute link with the full URL to the style sheet.

--
Ed Mullen
http://edmullen.net
http://mozilla.edmullen.net
http://abington.edmullen.net
Jan 24 '06 #7
Frances wrote:

it all checks fine, got no errors or warnings.. however Firefox is not
reading stylesheet, for some reason.. two examples of errors I get in JS
console:

Error: Unexpected end of file while searching for
closing } of invalid rule set.

Error: Unexpected end of file while searching
for ',' or '{'. Ruleset ignored due to bad selector.

These are basic *Javascript* syntax errors, not CSS since they are in
the JS console. You have a missing closing brace ("}") somewhere in your
"Javascript* code.

--
jmm (hyphen) list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)
Jan 24 '06 #8
Els
Ed Mullen wrote:
Frances wrote:
Els wrote:
Frances wrote:
Mark Parnell wrote:
> Deciding to do something for the good of humanity, Frances
> <fd***@yahoo.com> declared in
> comp.infosystems.www.authoring.stylesheets:
>
>> I have done css for Firefox many times, have never encountered
>> this.. would appreciate some leads..
>
> A URL to the CSS file in question would make it much easier.

thanks... http://www.francesdelrio.com/cc/viewer.css

And what is the page that should use that stylesheet?
First I was guessing your main page, but that one doesn't even have a
reference to the stylesheet. Then I figured it would be about the page
http://www.francesdelrio.com/cc/, but that one is referencing a
different stylesheet. So.. which page is it that doesn't let Firefox
read the stylesheet?


I can't post code for pg calling stylesheet (this is for work... doesn't
even go in path I posted earlier for stylesheet, I just stylesheet there
yesterday to check css-syntax on line at the w3c site..), but call to
stylesheet is as follows:

<LINK rel="stylesheet" type="text/css" href="viewer.css">
as you can see, nothing fancy, nothing unusual... thank you very much..


Hard to tell without a look at the actual server environment you are
seeing the error on. But, I'd suspect that possibly the server is
sending the wrong MIME type for the style sheet OR, possibly, that the
relative link in the HTML reference is not resolving correctly. Try an
absolute link with the full URL to the style sheet.


No, the server is sending the correct MIME type.
My wild guess is, that there is a syntax error in the JavaScript on
the HTML page, and the stylesheet is referenced *after* that
JavaScript, and therefore isn't recognised.
Frances - try taking out all the JavaScript from the <head> on your
HTML page - does the problem persist then?

--
Els http://locusmeus.com/
Sonhos vem. Sonhos vão. O resto é imperfeito.
- Renato Russo -
Now playing: Spargo - Hip Hap Hop
Jan 24 '06 #9
Els wrote:
Ed Mullen wrote:
Frances wrote:
Els wrote:

Frances wrote:

>Mark Parnell wrote:
>
>>Deciding to do something for the good of humanity, Frances
>><fd***@yahoo.com> declared in
>>comp.infosystems.www.authoring.stylesheets:
>>
>>
>>>I have done css for Firefox many times, have never encountered
>>>this.. would appreciate some leads..
>>
>>A URL to the CSS file in question would make it much easier.
>
>thanks... http://www.francesdelrio.com/cc/viewer.css

And what is the page that should use that stylesheet?
First I was guessing your main page, but that one doesn't even have a
reference to the stylesheet. Then I figured it would be about the page
http://www.francesdelrio.com/cc/, but that one is referencing a
different stylesheet. So.. which page is it that doesn't let Firefox
read the stylesheet?

I can't post code for pg calling stylesheet (this is for work... doesn't
even go in path I posted earlier for stylesheet, I just stylesheet there
yesterday to check css-syntax on line at the w3c site..), but call to
stylesheet is as follows:

<LINK rel="stylesheet" type="text/css" href="viewer.css">
as you can see, nothing fancy, nothing unusual... thank you very much..


Hard to tell without a look at the actual server environment you are
seeing the error on. But, I'd suspect that possibly the server is
sending the wrong MIME type for the style sheet OR, possibly, that the
relative link in the HTML reference is not resolving correctly. Try an
absolute link with the full URL to the style sheet.

No, the server is sending the correct MIME type.
My wild guess is, that there is a syntax error in the JavaScript on
the HTML page, and the stylesheet is referenced *after* that
JavaScript, and therefore isn't recognised.
Frances - try taking out all the JavaScript from the <head> on your
HTML page - does the problem persist then?


there is no JS BEFORE call to stylesheet.. also if error is

Error: Unexpected end of file while searching for ',' or '{'.
Ruleset ignored due to bad selector.
Source File: file:///T:/_mac/Pres110886_TOL_Altera/content/template/main.css
Line: 1

and I click on ref to .css file it takes me to .css file.. how can this
be a JS error? ('Ruleset' is a css thing, right?)
(took out JS inside <head> problem persists..)

this is truly baffling, it's like FF is not finding stylesheet.. thanks
again.. Frances
Jan 24 '06 #10
VK

Jim Moe wrote:
Frances wrote:

it all checks fine, got no errors or warnings.. however Firefox is not
reading stylesheet, for some reason.. two examples of errors I get in JS
console:

Error: Unexpected end of file while searching for
closing } of invalid rule set.

Error: Unexpected end of file while searching
for ',' or '{'. Ruleset ignored due to bad selector.

These are basic *Javascript* syntax errors, not CSS since they are in
the JS console. You have a missing closing brace ("}") somewhere in your
"Javascript* code.


Unfortunately Firefox dumps in JavaScript console all its complains
about the life - layout, script and style all together.

<http://www.google.com> main page produces exactly the same paired
error:
Error: Selector expected. Ruleset ignored due to bad selector.
Error: Unexpected end of file while searching for closing } of
invalid rule set.

Here is the minimum extracts from Google.com to reproduce the error (as
you can see nothing about script):

<html>
<head>
<title>Untitled Document</title>
<style><!--
body,td,a,p,.h{font-family:arial,sans-serif;}
..h{font-size: 20px;}
..q{color:#0000cc;}
//-->
</style>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
</head>
<body>
</body>
</html

If some CSS expert could explain what makes Firefox so upset that would
be great.

Jan 24 '06 #11
Els
Frances wrote:
Els wrote:
Ed Mullen wrote:
Frances wrote:

Els wrote:

>Frances wrote:
>
>>Mark Parnell wrote:
>>
>>>Deciding to do something for the good of humanity, Frances
>>><fd***@yahoo.com> declared in
>>>comp.infosystems.www.authoring.stylesheets:
>>>
>>>
>>>>I have done css for Firefox many times, have never encountered
>>>>this.. would appreciate some leads..
>>>
>>>A URL to the CSS file in question would make it much easier.
>>
>>thanks... http://www.francesdelrio.com/cc/viewer.css
>
>And what is the page that should use that stylesheet?
>First I was guessing your main page, but that one doesn't even have a
>reference to the stylesheet. Then I figured it would be about the page
>http://www.francesdelrio.com/cc/, but that one is referencing a
>different stylesheet. So.. which page is it that doesn't let Firefox
>read the stylesheet?

I can't post code for pg calling stylesheet (this is for work... doesn't
even go in path I posted earlier for stylesheet, I just stylesheet there
yesterday to check css-syntax on line at the w3c site..), but call to
stylesheet is as follows:

<LINK rel="stylesheet" type="text/css" href="viewer.css">
as you can see, nothing fancy, nothing unusual... thank you very much..

Hard to tell without a look at the actual server environment you are
seeing the error on. But, I'd suspect that possibly the server is
sending the wrong MIME type for the style sheet OR, possibly, that the
relative link in the HTML reference is not resolving correctly. Try an
absolute link with the full URL to the style sheet.


No, the server is sending the correct MIME type.
My wild guess is, that there is a syntax error in the JavaScript on
the HTML page, and the stylesheet is referenced *after* that
JavaScript, and therefore isn't recognised.
Frances - try taking out all the JavaScript from the <head> on your
HTML page - does the problem persist then?


there is no JS BEFORE call to stylesheet.. also if error is

Error: Unexpected end of file while searching for ',' or '{'.
Ruleset ignored due to bad selector.
Source File: file:///T:/_mac/Pres110886_TOL_Altera/content/template/main.css
Line: 1

and I click on ref to .css file it takes me to .css file.. how can this
be a JS error? ('Ruleset' is a css thing, right?)
(took out JS inside <head> problem persists..)

this is truly baffling, it's like FF is not finding stylesheet..


Is file:///T:/_mac/Pres110886_TOL_Altera/content/template/main.css the
same file as http://www.francesdelrio.com/cc/viewer.css ? Is it served
from the same server? I said earlier that it was sent with the correct
MIME type, but that was on the server that serves
http://www.francesdelrio.com/cc/viewer.css. I don't know anything
about your local server of course. If you have the Web Developer
Toolbar installed in FF, check the MIME type your CSS file is served
with, by clicking 'Information' and then 'Page Information' in the
Developer Toolbar.

--
Els http://locusmeus.com/
Sonhos vem. Sonhos vão. O resto é imperfeito.
- Renato Russo -
Now playing: Dr. Feelgood - Case Of The Shakes, A
Jan 24 '06 #12
Els
VK wrote:
Jim Moe wrote:
Frances wrote:

it all checks fine, got no errors or warnings.. however Firefox is not
reading stylesheet, for some reason.. two examples of errors I get in JS
console:

Error: Unexpected end of file while searching for
closing } of invalid rule set.

Error: Unexpected end of file while searching
for ',' or '{'. Ruleset ignored due to bad selector.

These are basic *Javascript* syntax errors, not CSS since they are in
the JS console. You have a missing closing brace ("}") somewhere in your
"Javascript* code.


Unfortunately Firefox dumps in JavaScript console all its complains
about the life - layout, script and style all together.

<http://www.google.com> main page produces exactly the same paired
error:
Error: Selector expected. Ruleset ignored due to bad selector.
Error: Unexpected end of file while searching for closing } of
invalid rule set.

Here is the minimum extracts from Google.com to reproduce the error (as
you can see nothing about script):

<html>
<head>
<title>Untitled Document</title>
<style><!--
body,td,a,p,.h{font-family:arial,sans-serif;}
.h{font-size: 20px;}
.q{color:#0000cc;}
//-->
</style>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
</head>
<body>
</body>
</html

If some CSS expert could explain what makes Firefox so upset that would
be great.


Well, I wouldn't use <!-- after <style>, nor //--> before </style>
I also wouldn't put the content type meta after the style element, but
that may be personal preference.
However, that piece of code doesn't do anything to my Firefox. Just
displays the empty page as expected.

--
Els http://locusmeus.com/
Sonhos vem. Sonhos vão. O resto é imperfeito.
- Renato Russo -
Now playing: Dr. Feelgood - Blues Jam - Oil City Sheiks
Jan 24 '06 #13
VK

Els wrote:
VK wrote:
Jim Moe wrote:
Frances wrote:

it all checks fine, got no errors or warnings.. however Firefox is not
reading stylesheet, for some reason.. two examples of errors I get in JS
console:

Error: Unexpected end of file while searching for
closing } of invalid rule set.

Error: Unexpected end of file while searching
for ',' or '{'. Ruleset ignored due to bad selector.

These are basic *Javascript* syntax errors, not CSS since they are in
the JS console. You have a missing closing brace ("}") somewhere in your
"Javascript* code.


Unfortunately Firefox dumps in JavaScript console all its complains
about the life - layout, script and style all together.

<http://www.google.com> main page produces exactly the same paired
error:
Error: Selector expected. Ruleset ignored due to bad selector.
Error: Unexpected end of file while searching for closing } of
invalid rule set.

Here is the minimum extracts from Google.com to reproduce the error (as
you can see nothing about script):

<html>
<head>
<title>Untitled Document</title>
<style><!--
body,td,a,p,.h{font-family:arial,sans-serif;}
.h{font-size: 20px;}
.q{color:#0000cc;}
//-->
</style>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
</head>
<body>
</body>
</html

If some CSS expert could explain what makes Firefox so upset that would
be great.


Well, I wouldn't use <!-- after <style>, nor //--> before </style>
I also wouldn't put the content type meta after the style element, but
that may be personal preference.
However, that piece of code doesn't do anything to my Firefox. Just
displays the empty page as expected.


This Whatever_It_Is acts up only for Firefox 1.5 (not for lower
versions)

Go to Tools > JavaScript Console
Press Clear
Load the testcase (or simply go to http://www.google.com)
Go to Tools > JavaScript Console again

Now you have two errors there:
Error: Selector expected. Ruleset ignored due to bad selector.
Error: Unexpected end of file while searching for closing } of invalid
rule set.

Indeed if we remove the unnecessary comment wrapper the error seems to
disappear (call Google :-).
At the same time a page like this does *not* lead to any error:

<html>
<head>
<title>Untitled Document</title>
<style>
<!--
body { background-color: #FFFFFF}
-->
</style>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
</head>
<body>
</body>
</html>

So Firefox 1.5 fails not on comment within style itself, but on some
combination of rule declarations and comments.

So what is the magic difference between erroneus:
<style><!--
body,td,a,p,.h{font-family:arial,sans-serif;}
..h{font-size: 20px;}
..q{color:#0000cc;}
//-->
</style>

and Ok'ed:

<style>
<!--
body { background-color: #FFFFFF}
-->
</style>

P.S. In any case seems an instability bug to report.

Jan 24 '06 #14
VK

VK wrote:
This Whatever_It_Is acts up only for Firefox 1.5 (not for lower
versions)

Go to Tools > JavaScript Console
Press Clear
Load the testcase (or simply go to http://www.google.com)
Go to Tools > JavaScript Console again

Now you have two errors there:
Error: Selector expected. Ruleset ignored due to bad selector.
Error: Unexpected end of file while searching for closing } of invalid
rule set.

Indeed if we remove the unnecessary comment wrapper the error seems to
disappear (call Google :-).
At the same time a page like this does *not* lead to any error:

<html>
<head>
<title>Untitled Document</title>
<style>
<!--
body { background-color: #FFFFFF}
-->
</style>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
</head>
<body>
</body>
</html>

So Firefox 1.5 fails not on comment within style itself, but on some
combination of rule declarations and comments.

So what is the magic difference between erroneus:
<style><!--
body,td,a,p,.h{font-family:arial,sans-serif;}
.h{font-size: 20px;}
.q{color:#0000cc;}
//-->
</style>

and Ok'ed:

<style>
<!--
body { background-color: #FFFFFF}
-->
</style>
Just got it! Last Firefox doesn't tolerate anymore JavaScript-style
escaped closing part of comment:
<style><!--
//--></style>
leads to error

<style><!--
--></style>
still OK
P.S. In any case seems an instability bug to report.


Screw no. Anyone is welcome though to harass Google to correct their
HTML (I just did).

Jan 24 '06 #15
Els
VK wrote:
Els wrote:
VK wrote:
Unfortunately Firefox dumps in JavaScript console all its complains
about the life - layout, script and style all together.

<http://www.google.com> main page produces exactly the same paired
error:
Error: Selector expected. Ruleset ignored due to bad selector.
Error: Unexpected end of file while searching for closing } of
invalid rule set.

Here is the minimum extracts from Google.com to reproduce the error (as
you can see nothing about script):

<html>
<head>
<title>Untitled Document</title>
<style><!--
body,td,a,p,.h{font-family:arial,sans-serif;}
.h{font-size: 20px;}
.q{color:#0000cc;}
//-->
</style>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
</head>
<body>
</body>
</html

If some CSS expert could explain what makes Firefox so upset that would
be great.
Well, I wouldn't use <!-- after <style>, nor //--> before </style>
I also wouldn't put the content type meta after the style element, but
that may be personal preference.
However, that piece of code doesn't do anything to my Firefox. Just
displays the empty page as expected.


This Whatever_It_Is acts up only for Firefox 1.5 (not for lower
versions)


I have 1.5.
Go to Tools > JavaScript Console
Press Clear
Load the testcase (or simply go to http://www.google.com)
Go to Tools > JavaScript Console again
Yup, now I see errors. I thought however, that the OP was complaining
about the stylesheet not being read, i.e. not picked up by the HTML
page.
Indeed if we remove the unnecessary comment wrapper the error seems to
disappear (call Google :-).
At the same time a page like this does *not* lead to any error: <style>
<!--
body { background-color: #FFFFFF}
-->
</style> So Firefox 1.5 fails not on comment within style itself, but on some
combination of rule declarations and comments.
Just the //. And isn't //--> a JavaScript tag?
P.S. In any case seems an instability bug to report.


Not imo. Just don't use JavaScript tags in your HTML or CSS and you're
fine ;-)

--
Els http://locusmeus.com/
Sonhos vem. Sonhos vão. O resto é imperfeito.
- Renato Russo -
Now playing: Dr. Feelgood - Mad Man Blues
Jan 24 '06 #16
Els wrote:
Frances wrote:

Els wrote:
Ed Mullen wrote:
Frances wrote:
>Els wrote:
>
>
>>Frances wrote:
>>
>>
>>>Mark Parnell wrote:
>>>
>>>
>>>>Deciding to do something for the good of humanity, Frances
>>>><fd***@yahoo.com> declared in
>>>>comp.infosystems.www.authoring.stylesheets:
>>>>
>>>>
>>>>
>>>>>I have done css for Firefox many times, have never encountered
>>>>>this.. would appreciate some leads..
>>>>
>>>>A URL to the CSS file in question would make it much easier.
>>>
>>>thanks... http://www.francesdelrio.com/cc/viewer.css
>>
>>And what is the page that should use that stylesheet?
>>First I was guessing your main page, but that one doesn't even have a
>>reference to the stylesheet. Then I figured it would be about the page
>>http://www.francesdelrio.com/cc/, but that one is referencing a
>>different stylesheet. So.. which page is it that doesn't let Firefox
>>read the stylesheet?
>
>I can't post code for pg calling stylesheet (this is for work... doesn't
>even go in path I posted earlier for stylesheet, I just stylesheet there
>yesterday to check css-syntax on line at the w3c site..), but call to
>stylesheet is as follows:
>
><LINK rel="stylesheet" type="text/css" href="viewer.css">
>as you can see, nothing fancy, nothing unusual... thank you very much..

Hard to tell without a look at the actual server environment you are
seeing the error on. But, I'd suspect that possibly the server is
sending the wrong MIME type for the style sheet OR, possibly, that the
relative link in the HTML reference is not resolving correctly. Try an
absolute link with the full URL to the style sheet.

No, the server is sending the correct MIME type.
My wild guess is, that there is a syntax error in the JavaScript on
the HTML page, and the stylesheet is referenced *after* that
JavaScript, and therefore isn't recognised.
Frances - try taking out all the JavaScript from the <head> on your
HTML page - does the problem persist then?


there is no JS BEFORE call to stylesheet.. also if error is

Error: Unexpected end of file while searching for ',' or '{'.
Ruleset ignored due to bad selector.
Source File: file:///T:/_mac/Pres110886_TOL_Altera/content/template/main.css
Line: 1

and I click on ref to .css file it takes me to .css file.. how can this
be a JS error? ('Ruleset' is a css thing, right?)
(took out JS inside <head> problem persists..)

this is truly baffling, it's like FF is not finding stylesheet..

Is file:///T:/_mac/Pres110886_TOL_Altera/content/template/main.css the
same file as http://www.francesdelrio.com/cc/viewer.css ? Is it served
from the same server? I said earlier that it was sent with the correct
MIME type, but that was on the server that serves
http://www.francesdelrio.com/cc/viewer.css. I don't know anything
about your local server of course. If you have the Web Developer
Toolbar installed in FF, check the MIME type your CSS file is served
with, by clicking 'Information' and then 'Page Information' in the
Developer Toolbar.


Web Developer tool for FF.. sounds interesting.. will certainly check it
out... (any url(s) off-hand? searched google for "firefox web
developer tool".. went to mozilla.org entry but not found..) thank you..

Jan 24 '06 #17
Els
Frances wrote:
Web Developer tool for FF.. sounds interesting.. will certainly check it
out... (any url(s) off-hand? searched google for "firefox web
developer tool".. went to mozilla.org entry but not found..) thank you..


http://chrispederick.com/work/webdeveloper/

--
Els http://locusmeus.com/
Sonhos vem. Sonhos vão. O resto é imperfeito.
- Renato Russo -
Now playing: Mötley Crüe - Rattlesnake Shake
Jan 24 '06 #18
VK wrote:
So Firefox 1.5 fails not on comment within style itself, but on some
combination of rule declarations and comments.

So what is the magic difference between erroneus:
<style><!--
body,td,a,p,.h{font-family:arial,sans-serif;}
.h{font-size: 20px;}
.q{color:#0000cc;}
//-->
</style>

and Ok'ed:

<style>
<!--
body { background-color: #FFFFFF}
-->
</style>


The difference is quite simple & fairly easy to find: click on the
link Firefox provides in the console - it will highlight the error.

The error is the difference between:
-->
and
//-->

The "bad selector" is //, which is NOT a CSS comment
(http://www.w3schools.com/css/css_syntax.asp), and therefore is not
being read as one. Eliminate the // and the problem goes away.

I have found this behavior consistent with the test cases I've tried.

I don't think that's a Firefox bug. Rather, it's a coding error.

Jan 24 '06 #19
VK wrote:

Just got it! Last Firefox doesn't tolerate anymore JavaScript-style
escaped closing part of comment:
<style><!--
//--></style>
leads to error

<style><!--
--></style>
still OK


I should have kept reading :)

Jan 24 '06 #20

Els wrote:
Frances wrote:
Web Developer tool for FF.. sounds interesting.. will certainly check it
out... (any url(s) off-hand? searched google for "firefox web
developer tool".. went to mozilla.org entry but not found..) thank you..
http://chrispederick.com/work/webdeveloper/

--
Els http://locusmeus.com/
Sonhos vem. Sonhos vo. O resto imperfeito.
- Renato Russo -
Now playing: Mtley Cre - Rattlesnake Shake

From http://chrispederick.com/work/webdeveloper/ I downloaded

webdeveloper.xpi
What in heaven's name is an .xpi file?

When I tried to open it, I was asked for the name of the program to
open it with.

I don't know the answer to that

Jan 25 '06 #21
Trevor L. wrote:
Els wrote:
Frances wrote:
Web Developer tool for FF.. sounds interesting.. will certainly checkit
out... (any url(s) off-hand? searched google for "firefox web
developer tool".. went to mozilla.org entry but not found..) thank you..

http://chrispederick.com/work/webdeveloper/

--
Els http://locusmeus.com/
Sonhos vem. Sonhos vo. O resto imperfeito.
- Renato Russo -
Now playing: Mtley Cre - Rattlesnake Shake

From http://chrispederick.com/work/webdeveloper/ I downloaded

webdeveloper.xpi
What in heaven's name is an .xpi file?

When I tried to open it, I was asked for the name of the program to
open it with.

I don't know the answer to that


Drag it from Windows Explorer and drop it into a Firefox browser window.
It's a zipped archive with automatic install. FF will ask if you want
to install it.

--
Ed Mullen
http://edmullen.net
http://mozilla.edmullen.net
http://abington.edmullen.net
Jan 25 '06 #22
VK wrote:

These are basic *Javascript* syntax errors, not CSS since they are in
the JS console. You have a missing closing brace ("}") somewhere in your
"Javascript* code.


Unfortunately Firefox dumps in JavaScript console all its complains
about the life - layout, script and style all together.

<style><!--
//-->
</style>

If some CSS expert could explain what makes Firefox so upset that would
be great.

Ah, I see what I missed. That is a Javascript comment delimiter in a
<style> element, CSS. Different languages. That is, of course, incorrect.
Previously, though, there was nowhere to send a message about CSS errors,
they were silently handled. I guess Firefox decided the JS console was as
good a place as any.
Firefox is confused because it thinks a new ruleset is being declared
after the last one, ".q{color:#0000cc;}". There is the closing brace, "}",
then what appears to be a new selector, "//-->", with no ruleset following
it. Thus the error message.

--
jmm (hyphen) list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)
Jan 25 '06 #23
On 2006-01-24, Jim Moe <jm***************@sohnen-moe.com> wrote:
Frances wrote:

it all checks fine, got no errors or warnings.. however Firefox is not
reading stylesheet, for some reason.. two examples of errors I get in JS
console:

Error: Unexpected end of file while searching for
closing } of invalid rule set.

Error: Unexpected end of file while searching
for ',' or '{'. Ruleset ignored due to bad selector.

These are basic *Javascript* syntax errors, not CSS since they are in
the JS console. You have a missing closing brace ("}") somewhere in your
"Javascript* code.


I don't think javascript has selectors or rulesets.

--

Bye.
Jasen
Jan 25 '06 #24
Jim Moe wrote:

Previously, though, there was nowhere to send a message about CSS errors,
they were silently handled. I guess Firefox decided the JS console was as
good a place as any.


FYI, mozilla browsers have been dumping all kinds of error messages in
the JS console for years. It's nothing new, you probably just haven't
noticed before.

--
Reply email address is a bottomless spam bucket.
Please reply to the group so everyone can share.
Jan 25 '06 #25
Deciding to do something for the good of humanity, Jim Moe
<jm***************@sohnen-moe.com> declared in
comp.infosystems.www.authoring.stylesheets:
Previously, though, there was nowhere to send a message about CSS errors,
they were silently handled. I guess Firefox decided the JS console was as
good a place as any.


JS, CSS and XML errors are all reported through the JS console.

I find this extension very handy:
https://addons.mozilla.org/extension...refox&numpg=50

--
Mark Parnell
================================================== ===
Att. Google Groups users - this is your last warning:
http://www.safalra.com/special/googlegroupsreply/
Jan 26 '06 #26

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Jeremy Epstein | last post: by
6 posts views Thread by Geoff | last post: by
87 posts views Thread by expertware | last post: by
5 posts views Thread by SPE - Stani's Python Editor | last post: by
7 posts views Thread by Coder | last post: by
12 posts views Thread by amit | last post: by
6 posts views Thread by scotty | last post: by
3 posts views Thread by SAL | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
reply views Thread by harlem98 | last post: by
reply views Thread by harlem98 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.