PDA

View Full Version : google search parse errors



Kodah
Jun 26th, 2009, 04:58 PM
Hi,
I have completed a project (for the third time) for a client. The site uses google search. The problem is that I get parse errors on google elements which I don't seem to have any control over. The errors are much like the errors generated on these forums. like "Error in parsing value for 'display'. Declaration dropped" and the following link refers to www.google.com/ blaha/blah/... If I can't fix these errors ie will always be in quirk mode, correct?

I don't really want or feel that it's necessary to post the url to the site inquestion since similar errors are present here. I have breifly searched the archives for tips but have not really found any. Any help will be apreciated.

abduraooft
Jun 26th, 2009, 05:05 PM
"Error in parsing value for 'display'. Declaration dropped" Is that message from the w3's CSS validator?

Kodah
Jun 26th, 2009, 05:07 PM
no, it's from firefox developer tools

Apostropartheid
Jun 26th, 2009, 06:18 PM
Firefox's Developer's Tools !== the real world. I don't use Firefox so I can't see the error. Does it come up when you validate your CSS? If not, what exactly is the problem?

And, also, your idea of how Quirks mode is triggered is quite wrong. This should clarify (http://www.quirksmode.org/css/quirksmode.html).

Kodah
Jun 26th, 2009, 07:17 PM
Thanks Cyanlight for the link it did further explain quirks mode and was helpful my point is that (from the link) "In IE, the rendering mode decides which box model it follows. In quirks mode it uses the traditional model, in strict mode the W3C model."

I read somewhere, although I can't find it for the life of me now, that errors on the page triggers quirk mode in IE, therefore the box model becomes an issue.

Kodah
Jun 26th, 2009, 09:25 PM
Ok, eventhough FF is not the w3c validator the google errors exist.

all other errors were resolved (but it destroyed the page) and the only errors and warnings left are related to these two lines :
<script type="text/javascript" src="http://www.google.com/coop/cse/t13n?form=cse-search-box&t13n_langs=en"></script>
<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
It seems that the ampersand should be escaped, I can find out the proper way to escape this but will it mess up the search script? I didn't remove any characters when I added it to the page.
Also it seems the xml parser was expecting a delimiter';' it didn't find.

Like I said, I've built this site like three times. First in php for easy maintenance but now it's just straight html so that the "web master" can handle it. Yet I continually find stray bits of code here and there, missing or additional tags etc...

Apostropartheid
Jun 26th, 2009, 10:44 PM
The proper way to escape an ampersand is &amp;

Kodah
Jun 27th, 2009, 05:56 AM
Hello delimiter :rolleyes: