-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
The problem is demonstrated in the attached movie file :
Create a new application, and open home.xhtml and move to the end.
Start typing <h:outputte and when auto complete pops up, select outputText, the tag is put into the document and the value="" attribute is also added. The caret is placed between the double quotes and the auto completion selection pops up.
Initially, the list of values in the auto completion box consists of everything that should be there, but it is not wrapped in an EL expression #
{ ... } (i.e. "conversation" is there, but not "#{conversation}"). As soon as you type #{ in the page, the code completion dialog filters out most of the values, except the basic EL expressions (#{applicationScope}, #{param}, #{facesContext}, #{cookie}).To get proper code suggestions, you need to close the code completion pop up, and re-open it to get the right list of values, i.e. Seam generated suggestions,
It almost looks like in the initial pop up, the values are there, but they are not wrapped in #{ ... }
, while when you bring it up again, the values are there, and they have the #
{ ... }This is mostly a problem because it happens in the auto-completion box that is popped up when the IDE auto completes a JSF tag.
- relates to
-
JBIDE-2227 CA shows useless proposals when we editing style for h:output text in seam project
- Closed
-
JBIDE-2277 CA proposals for jsf variables and seam variables is different
- Closed