262662 – autocomplete does not work on last css entry before start of nested selector declaration

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 262662 - autocomplete does not work on last css entry before start of nested selector declaration

Summary: autocomplete does not work on last css entry before start of nested selector ...

Status:	NEW

Alias:	None

Product:	web
Classification:	Unclassified
Component:	CSS Preprocessors (SASS, LESS, ...) (show other bugs)
Version:	8.2
Hardware:	PC Mac OS X

Importance:	P3 normal (vote)
Assignee:	Milutin Kristofic

URL:
Keywords:

Depends on:
Blocks:

Reported:	2016-07-02 18:00 UTC by dylanv
Modified:	2016-07-02 18:00 UTC (History)
CC List:	1 user (show)

See Also:
Issue Type:	DEFECT
Exception Reporter:

Attachments
example of the bug happening (47.30 KB, image/png) 2016-07-02 18:00 UTC, dylanv	Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description dylanv 2016-07-02 18:00:10 UTC

Created attachment 160238 [details]
example of the bug happening

A consistent issue with the SASS editor, is that it does not autocomplete any properties if the property is the last property before a new nested class is about to start. The screenshot attached shows this problem as the IDE should auto-complete fields including background-color but instead it only lists css selectors. This is only an issue for the last selector defined, aka if I were a line above in the screenshot and entered something directly above "display:flex" the problem would not occur and i would get a list of all possible properties.

This might be related to a bug which I am probably going to log next that involves the editor constantly throwing an exception when using the developer version of netbeans on every single keypress. For now, i have all errors turned off because i cannot use the IDE when that start happening. This bug that I am now talking about usually happens when I start having many many sass files, so its hard to reproduce.