Would you please handle this as priority 2. It is a regression (worked in version 6.9.1). I am a bit concerned otherwise because there are currently ca 4,000 open priority 3 bugs.

The result of this drives me creazy. If a closing div is missing deep inside a hierarchy, then my validator complains about the outermost div not being closed. I open the file in NetBeans 6,9 to fix the error, but I can't because again, it complains at the end of the file.

So hours after editing the file when I did not notice the error, I can't systematically find that div that is not closed, and I get bloody eyes trying to fix this.

fixed in web-main#d4b5e51c079b, releases/release701#03eb28eae7dd

The problem was one of the element's attribute w/o a value inside the code. This problem was shown as a warning so it likely escaped your notice. Since such problem is fatal from the xml point of view, further error analysis was disabled.

I've changed the html validator hints processing so the fatal errors never fals sto the build-in categories where they might be configured as warnings but always are shown as errors. I've also added some warning to the error messages which points out to the fact that file with such error cannot be properly processed by netbeans (and of course by the using application itself).

I hope this helps.

Integrated into 'main-golden'
Changeset: http://hg.netbeans.org/main-golden/rev/
User: 
Log:

Thanks a lot.

verified