apache / apache/grails-intellij-plugin

CSS Autocomplete in GSP for classes fails with if <style> tag present

Open
#230 0 comments 0 reactions 0 assignees View on GitHub
bug imported-from-youtrack
Dominant language
Java
Stars
17
Forks
4
Avg merge
5d 15h
Merged PRs (30d)
4

Description

Grails 2.4.4 with Asset pipeline (important since stylesheets are imported differently from previous usage of grails-app)

Using layouts to mesh templates together css is imported from the parent template. Adding a <style> tag to the head of the working document disables the autocomplete feature for class="" attributes on elements. Moving the content of the style tag to a separate file and importing it via <asset:stylesheet/> does not void the autocomplete list. Simply having an empty <style> within the gsp is enough to override the autocomplete feature.

/CSSTestProject/grails-app/views/testDO/index.gsp <- CSS autocomplete works (no style tag)

./CSSTestProject/grails-app/views/testDO/show.gsp <- CSS autocomplete "No suggestions" (with style tag)

---

*Imported from [IDEA-148360](https://youtrack.jetbrains.com/issue/IDEA-148360) · Type: Bug · Votes: 0*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the difference between grails-app/views/testDO/index.gsp and grails-app/views/testDO/show.gsp, including the empty tag and the asset:stylesheet alternative. Trace the GSP CSS class completion path and verify that class="" suggestions still appear when an inline style tag is present.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.