manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1215) Tag parsing in script tags shouldn't recognize "<" but does
Date Wed, 24 Jun 2015 14:34:09 GMT


Karl Wright commented on CONNECTORS-1215:

The issue is complex because according to spec the code is doing the right thing.  Typically,
<script> blocks look something like this:

<script ...>



The reason for the comment area is because without it, tags within the script block are supposed
to be recognized as such, even if they are ignored.  Within comments, this does not happen,
of course, which is why comments are used.

I don't believe it is a real standard, but some browsers try to interpret script blocks differently
even when no comment is given.  We can try to emulate that behavior but it is likely that
our emulation will not work for all web pages, since it's not a standard.  Exploring how this
works on various browsers would be the first step.  Specifically, if you do something like

<script ...>

foo = "<script></script>";
bar = "hello";


... what happens?  Does the script end at the first </script>, or the second?  And,
in what browsers?

Until we get more clarity it's going to be hard to do a feature that actually helps rather
than hurts...

> Tag parsing in script tags shouldn't recognize "<" but does
> -----------------------------------------------------------
>                 Key: CONNECTORS-1215
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Web connector
>    Affects Versions: ManifoldCF 1.9, ManifoldCF 2.1
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.10, ManifoldCF 2.2
> User says:
> "There appears to be a bug in the TagParseState when the comparison operator '<' 
is encountered in the body of  a script tag.  It appears to get flagged as an open tag and
then the next '</' closes it.  In my case, the next '</' is the script tag.  The ScriptParseState
chomps everything until it encounters a second </script> tag.
> A live link that demonstrates this bug is here:
> The '<' near line 2826 in the script body that begins near   line 2759 begins a new
tag 'arraykeywords.length' which gets closed by the '</' in the closing script tag.  The
ScriptParseState chomps all the html until it sees the end script tag near line 3385.
> At the moment, I'm not sure of a solution other than pushing the script tag handling
up to the TagParseState and treating it like CDATA is."

This message was sent by Atlassian JIRA

View raw message