This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Error triggered for <script> inside of <textarea> | ||
---|---|---|---|
Product: | web | Reporter: | bfrohs |
Component: | HTML Editor | Assignee: | Milutin Kristofic <mkristofic> |
Status: | NEW --- | ||
Severity: | normal | CC: | mfukala, vriha |
Priority: | P4 | ||
Version: | 7.3 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
bfrohs
2013-02-26 21:55:44 UTC
reproducible in trunk Is fn w/o name valid? In any case this is javascript editor issue as the same error appears in pure js file with "function (){} " content. (In reply to comment #2) > Is fn w/o name valid? In any case this is javascript editor issue as the same > error appears in pure js file with "function (){} " content. pls disregard :-) You are right, textarea element's content type is text so the content should not be treated as html content and hence colored and parsed by javascript editor. However the javascript embedding creation inside the script section is now based on lexical analysis only so there's no info about the parent element. Creation of the js embedding based on parser analysis is not convenient - we've already tried before few years and returned back to lexical only analysis. In theory I could keep the lexical based js embedding creation and remove the embedding from such areas based on parser result, but it seems to be to be quite complicated solution for IMHO marginal issue. I'm downgrading this to P4 if you do not mind. |