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 237622 - HTML Error checking hint cannot be removed/disabled
Summary: HTML Error checking hint cannot be removed/disabled
Status: RESOLVED WONTFIX
Alias: None
Product: web
Classification: Unclassified
Component: HTML Editor (show other bugs)
Version: 8.0.2
Hardware: PC Windows 7 x64
: P3 normal with 1 vote (vote)
Assignee: issues@web
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-24 13:17 UTC by Etzeitet
Modified: 2016-12-29 22:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screen shot of the annoying hint. (13.28 KB, image/png)
2013-10-24 13:17 UTC, Etzeitet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Etzeitet 2013-10-24 13:17:19 UTC
Created attachment 141520 [details]
Screen shot of the annoying hint.

In NetBeans IDE 7.4 (Build 201310111528) I have encountered an issue with one of the editor hints.

At the top of all my PHP documents I see the "HTML error checking for this file is disabled" hint [see annoyinggint.png]. I cannot for the life of me get this hint to go away.

No matter what option I choose the hint remains. The actual hint text switches between "HTML error checking for this file is disabled" and "enabled". Or it moans about not finding a DOCTYPE.

I have tried disabling HTML hints in the IDE's options, but this does nothing.

I then tried disabling ALL PHP and HTML hints, and this successfully gets rid of the "HTML error checking" hint, but the "HTML version of the code cannot be determined" hint remains.

It seems to me this is a defect if I cannot dismiss a hint I don't care about.
Comment 1 Marek Fukala 2014-07-16 13:13:11 UTC
As designed - the hint is there so you can possibly enable the html validation. The same mechanism is used for javascript error checking. It doesn't affect the status of the file.
Comment 2 DaH12 2016-10-29 14:38:05 UTC
It is clearly true that this hint doesn't affect the status of the file

However, as a general policy, it is good to 'resolve' all hints in a file before it is sent to production - when every file has a hint that can't be resolved, it prevents a 'no source code problems before committing' policy to be implemented (no problems except this hint doesn't really work)