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.
Create new JSP file use this code: ------------------------------------------------------------------- <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %> <c:choose> <c:when test="${customer.country == 'USA'}"> <div style="color:blue"> </c:when> <c:when test="${customer.country == 'Canada'}"> <div style="color:red"> </c:when> <c:otherwise> <div style="color:green"> </c:otherwise> </c:choose> CODE COLORED ACCORDING TO CUSTOMER COUNTRY </div> --------------------------------------------------------------------- first two div tags are underlined as unfinished, but the code is correct, because in HTML after processing just one of them will be
Jindro, please do not torture me with such issues. How can the editor know which or how many of the <div> tags will be in the generated page??? You cannot determine what will be the result of the runtime page execution. Please....... :-)
I understand the problem that we are not able to determine the runtime execution, but we should not show warning if we are not sure there is some problem in user's code. It's quite bothering to look on you well written web page and see warnings or errors in editor... The same can happen using imports or scriptlets... We should think of such problem at least in the future...
That would mean disable all html parser based features in templating languages, sure, it is an option. If you have a better idea go on and let me know, thanks.
there are cases, where we can find a problem while parsing HTML - in fresh HTML subtree, but we can not find problems when HTML tree is broken by some other language, would it be possible to check just parts of HTML code that are continual?
This could cause user confustions IMHO, sometimes error would be show, sometimes not on the same html code (with just a small piece of jsp or el). Jindro, can we discuss this in person next week? I will definitively not do anything related in 6.0, sorry.
There are many reports from users about this problem. I would propose at least add some option to disable this feature for users request. See my jspf file, that serves as footer - all end tags are started in page header or sidebar.
Created attachment 55232 [details] footer
I agree that under some circumstances the errors and warnings should be disabled. The question is how the UI should look like. 1) action in the editor popup menu 2) action in the annotation popup menu 3) action on the file status icon 4) some other UI? I can easily do #1 and maybe #2, the setting would be saved per file. The question is whether shouldn't be considered in some wider context (not only html can have this problem IMO).
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss