Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Why am I getting thousands of warning messages reading"Warning: Unexpected token in attribute selector: '!'. Source File: http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-US:official Line: 0""

more options

Once I open Firefox and go into Tools, Error Console, the following warning messages are generated continually Warning: Unexpected token in attribute selector: '!'. Source File: http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-US:official Line: 0 Warning: Unexpected token in attribute selector: '!'. Dangling combinator. Source File: http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-US:official Line: 0 Warning: Unexpected token in attribute selector: '!'. Dangling combinator. Source File: http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-US:official Line: 0 Warning: Unexpected token in attribute selector: '!'. Dangling combinator. Source File: http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-US:official Line: 0

Once I open Firefox and go into Tools, Error Console, the following warning messages are generated continually Warning: Unexpected token in attribute selector: '!'. Source File: http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-US:official Line: 0 Warning: Unexpected token in attribute selector: '!'. Dangling combinator. Source File: http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-US:official Line: 0 Warning: Unexpected token in attribute selector: '!'. Dangling combinator. Source File: http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-US:official Line: 0 Warning: Unexpected token in attribute selector: '!'. Dangling combinator. Source File: http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-US:official Line: 0

All Replies (1)

more options

This is happening to me as well. Disabling the McAfee SiteAdvisor plug-in seemed to stop the behavior.