Bug 338025

Description David Carver 2011-02-23 16:43:21 EST

I've tracked this down at least in the old XMLContentAssistProcessor around line 184, to the following bit of code:

					boolean showAttribute = true;
					showAttribute = showAttribute && beginsWith(getRequiredName(node, attrDecl), matchString.trim());
					AttrImpl attr = (AttrImpl) node.getAttributes().getNamedItem(getRequiredName(node, attrDecl));
					ITextRegion nameRegion = attr != null ? attr.getNameRegion() : null;
					// nameRegion.getEndOffset() + 1 is required to allow for
					// matches against the full name of an existing Attr
					showAttribute -s= showAttribute && ((attr == null) || ((nameRegion != null) && (sdRegion.getStartOffset(nameRegion) <= contentAssistRequest.getReplacementBeginPosition()) && (sdRegion.getStartOffset(nameRegion) + nameRegion.getLength() >= contentAssistRequest.getReplacementBeginPosition() + contentAssistRequest.getReplacementLength())));

The file in the xsl tools UI test, called simple.xsl can be used to reproduce the problem in the normal XML editor.

Load the file up.

Locate the line <xsl:value-of select="" />

Position the cursor right before the />

Press CTRL + SPACE

You do not get the disable-output-escaping attribute in the proposals list.

If you open the Content Model View, and expand out the value-of element. You will see that you should have two choices.

select
disable-output-escaping.

This is a regression possibly due to the way default values are now being handled for attributes.