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.

Bug 167228

Summary: HTML indentation seems to be confused in JSP files
Product: web Reporter: Jindrich Sedek <jsedek>
Component: HTML EditorAssignee: Milutin Kristofic <mkristofic>
Status: NEW ---    
Severity: blocker    
Priority: P4    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:

Description Jindrich Sedek 2009-06-17 12:31:11 UTC
use this code in JSP file:
---------------------------------
<html>
    <head>
        <title></title>
    </head>
    <body>
        <div>
            <div>
                <table class="axial">
                    <tr>
                        <td>${jdks}</td>
                    </tr>
                </table>
            </div>
        </div>|
    </body>
</html>
-------------------------------
press Enter at position of "|" -> indentation is incorrect - you get:
-------------------
 ...
        </div>
                 |
-------------------
removing expression language (line <td>${...}</td>) seems to fix the problem
Comment 1 Quality Engineering 2009-06-24 07:30:27 UTC
Integrated into 'main-golden', will be available in build *200906240201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/12c72cdad00f
User: mkuchtiak@netbeans.org
Log: #167228: resolve META-INF/wsdl folder by using J2EE persistence API
Comment 2 David Konecny 2011-02-01 20:23:53 UTC
This issue is tricky. Reindent of whole file will always work. But for single line indent there are several optimization in place and one of them is causing this problem. Removing optimization would solve this issue but it may also have negative performance impact (in certain scenarios). The right fix would be to enhance optimization to cover this case as well. That's doable but non trivial - indentation code is very complex. So unless there are other case where this fails or there is a strong demand to fix this I'm putting this issue on hold.