Extracted from the issue 179727 - [69cat] Code completion is slow
Getting CSS parser result automatically involves the error evaluation of the css rules which is not always necessary.
Making the semantic css error analysis lazy. Until one calls getDiagnostics() on the parser result it is not computed. In fact I'm not sure whether anyone else can call that method when the parser result is explicitly requested by PM.parse() from the completion thread before the completion shows the results. If this happens, some kind of parse levels would have to be added to the css parser result.
Integrated into 'main-golden', will be available in build *201104020400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Marek Fukala <email@example.com>
Log: #197314 - CSS completion blocked by CSS parser error analysis