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 243936 - Option to disable error badges in CSS
Summary: Option to disable error badges in CSS
Status: NEW
Alias: None
Product: web
Classification: Unclassified
Component: CSS Editor (show other bugs)
Version: 8.0
Hardware: All All
: P2 normal with 1 vote (vote)
Assignee: Milutin Kristofic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-19 12:37 UTC by leoquijano
Modified: 2014-10-06 13:27 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description leoquijano 2014-04-19 12:37:20 UTC
Hi, 

As mentioned in issue #226954:

I see that for Netbeans 8.0 there are two workaround for the error badges issues when using big libraries.

We have:
-J-Dnb.php.silent.error.badge=true
-J-Dnb.html.silent.error.badge=true

Both work perfectly. But CSS is still an issue. Even though there's a way of manually removing CSS errors according to issue #141181, the workaround is imperfect since:

1) For large projects, removing a CSS error reporting via the hint option, makes Netbeans reindex everything! Right now I have 7 open projects, each with versions of WordPress or other common PHP structures, and reindexing takes more than 1 hour. Considering that Netbeans reindex every time I add a CSS error exception, filtering out all error badges would take hours.

2) As with the HTML & PHP workarounds, I would like to keep getting the CSS errors but remove the badges ONLY. The hint filter mentioned in #141181 doesn't address this.

So I think this can be remedied by adding a new special option: 
-J-Dnb.css.silent.error.badge=true

I was looking for patches on the other two options, to see if I could do it myself (though I know nothing of the Netbeans codebase), but didn't seem to find it. Is this something that might be considered soon?

I know that Issue #238782 has a more permanent solution, but this issue is only for the workaround, a possibly faster issue and an option that would be good to have for completeness.

Thanks!