[Bug 29106] New: JavaScript is interpreted as HTML: logical operator "&&" is suggested to be written as "&&"

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29106

            Bug ID: 29106
           Summary: JavaScript is interpreted as HTML: logical operator
                    "&&" is suggested to be written as "&&"
           Product: Validator
           Version: HEAD
          Hardware: All
                OS: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: check
          Assignee: dave.null@w3.org
          Reporter: hakan.hildingsson@mobby.se
        QA Contact: www-validator-cvs@w3.org
  Target Milestone: ---

PAGE USED TO GET THIS ISSUE
[2015-09-01]
http://www.datatermgruppen.se/component/option,com_chronocontact/Itemid,107/

EXAMPLE OF OUTPUT
Warning character X is the first character of a delimiter but occurred as data
✉
This message may appear in several cases:

You tried to include the "<" character in your page: you should escape it as
"&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it
is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 99, column 31: character "&" is the first character of a delimiter but
occurred as data
                        el.$tmp.myTitle = (el.href && el.getTag() == 'a') ?
el.href.replace('http://…


SOURCE CODE THAT CAUSED THIS ISSUE
              1         2         3         4
     1234567890123456789012345678901234567890
  1: <!DOCTYPE ...>
  2: <html ...>
  3: <head>
     ...
 64: <script type="text/javascript">
     var ChronoTips = new Class({
 66:  options: {...},
 80:  initialize: function(elements, lasthope,options){...},

 98:  build: function(el){
>99:   el.$tmp.myTitle = (el.href && el.getTag() == 'a') ? el.href.replace('http://', '') : (el.rel || false);  <==
                        if (el.title){...
      ...
183: </scrip>
493: </head>
     ...
495: <body>
     ...
797: </body>
798: </html>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 1 September 2015 08:46:29 UTC