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 231872 - Detected errors in XHTML document are not reported as error in project tree
Summary: Detected errors in XHTML document are not reported as error in project tree
Status: NEW
Alias: None
Product: web
Classification: Unclassified
Component: HTML Editor (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Milutin Kristofic
Depends on:
Reported: 2013-06-26 21:27 UTC by ecerichter
Modified: 2014-10-06 13:27 UTC (History)
1 user (show)

See Also:
Exception Reporter:

screenshot of the issue (168.66 KB, image/png)
2013-06-26 21:33 UTC, ecerichter
Offending file (2.37 KB, text/html)
2013-06-26 21:36 UTC, ecerichter

Note You need to log in before you can comment on or make changes to this bug.
Description ecerichter 2013-06-26 21:27:27 UTC
Product Version = NetBeans IDE Dev (Build 201306252301)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0_21
Runtime = Java HotSpot(TM) 64-Bit Server VM 23.21-b01

I've this htm document with some XHTML errors (or not!), in the Action Items (and Editor) window, appears as error; in project tree, shows nothing wrong.
So, from my point of view, if this is really an error, then it should be noted either in Action Items, in Editor and in Project Tree.
If it is not an error, then should be noted as warning only.

Attached there is a screenshot of my NB and also the faulty htm (from tiny_mce library).


Comment 1 ecerichter 2013-06-26 21:33:03 UTC
Created attachment 136361 [details]
screenshot of the issue
Comment 2 ecerichter 2013-06-26 21:36:05 UTC
Created attachment 136362 [details]
Offending file
Comment 3 Vladimir Riha 2013-06-26 22:48:51 UTC
Reproducible, thank you for reporting

NetBeans IDE Dev (Build web-main-10912-on-20130626)
Comment 4 Marek Fukala 2013-06-27 15:00:03 UTC
I think it's bit different for HTML than for strictly checked languages like java. Most of the issues found can be easily relaxed by the browser so the app will still run. Some of the issues are really "light" (like obsolete attributes) so these are warning, some of them *may* really represent a problem (missing pair tag) so these are marked as error. I believe this is a good thing to distinguish these somehow, but still... the page will likely "run" w/o a problem. So the file as such is not marked as erroneous.

It *used to* behave like you proposed but people complained that their projects are all red but runs fine.

I agree that some kind of solution is necessary - either introduce sg. like fatal error, which will always badge the file, or add a new control to the hints configurator - sg. like "badge file" checkbox for each category.
Comment 5 Marek Fukala 2013-07-10 13:58:42 UTC
I'm sorry but I'm turing this into an enhancement as this requires changes in the underlying infrastructure. Svata Dedic already works on the stuff described in comment#4, but I do not know if there's any issue I can depend on. Svato? What is the progress/plan?