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: | Detected errors in XHTML document are not reported as error in project tree | ||
---|---|---|---|
Product: | web | Reporter: | ecerichter |
Component: | HTML Editor | Assignee: | Milutin Kristofic <mkristofic> |
Status: | NEW --- | ||
Severity: | normal | CC: | sdedic |
Priority: | P3 | ||
Version: | 7.4 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Attachments: |
screenshot of the issue
Offending file |
Description
ecerichter
2013-06-26 21:27:27 UTC
Created attachment 136361 [details]
screenshot of the issue
Created attachment 136362 [details]
Offending file
Reproducible, thank you for reporting NetBeans IDE Dev (Build web-main-10912-on-20130626) 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. 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? |