[NETBEANS-445] Many missing values for code completion of the CSS display property

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 8.2, 9.0, 11.2
• Fix Version/s: 12.0
• Component/s: web - CSS Editor
• Labels: autocompletion css css3 pull-request-available

Environment

Product Version: Apache NetBeans IDE Dev (Build incubator-netbeans-release-205-on-20180202)
Java: 1.8.0_162; Java HotSpot(TM) 64-Bit Server VM 25.162-b12
Runtime: Java(TM) SE Runtime Environment 1.8.0_162-b12
System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb)
User directory: C:\Users\johndoe\AppData\Roaming\NetBeans\dev
Cache directory: C:\Users\johndoe\AppData\Local\NetBeans\Cache\dev

• Assignee: Matthias Bläsing
• Reporter: Rick Hegarty
• Created: 05/Mar/18 18:35
• Updated: 03/Nov/20 15:45
• Resolved: 12/Mar/20 19:08

Description

Code completion offers many options for the value of the CSS display property when editing a CSS file (see the attached screen shot), but there are still many possible values that  are not supplied.

Based on the information provided in "CSS Display Module Level 3" (https://www.w3.org/TR/css-display-3) the following options should be added to code completion for the display property in NetBeans:

flow
flow-root
flex
grid
subgrid
ruby-base-container
ruby-text-container
contents
inline-flex
inline-grid

**Updated on 6/27/18:

[1] The problem with autocomplete for CSS is not confined to missing values for the display property. For example, no grid-... properties (e.g. grid-column-start) are suggested, nor is row-gap. The list of valid CSS properties and values used by autocomplete needs to be updated.

[2] If a CSS property is not suggested during auto-completion then its valid use in CSS code will be incorrectly reported as an error (e.g. "Unknown property grid-column-gap").

[3] A serious side effect of the previous issue is that genuine errors in CSS code may be much harder to identify because they are mixed in with bogus errors.

Since this issue is more extensive and serious than the initial report above I have raised the priority to Major, and also updated the affected versions to include 8.2.

Issue Links

• links to: GitHub Pull Request #2006