Community
Participate
Working Groups
This seems to be a bug that auto activation does not work in Javascript regions. Bug 305209 fixed this problem for Java regions in JSPs. JavaScript Development Tools Version: 1.2.0.v201005270528-7C78FGDF9JgLWLMBWz-Ose6 Build id: 20100615235519
Ian, you fixed this same bug in Java.
Created attachment 179108 [details] Fix Patch This patch makes it so auto activation for Javascript works in Javascript regions in both HTML and JSPs. To do this an implementation of StructuredContentAssistProcessor had to be created for JSDT that uses the JSDT content assist auto-activation preferences. Then JSDTStructuredTextViewerConfigurationJSP#getContentAssistProcessors and StructuredTextViewerConfigurationJSDT#getContentAssistProcessors had to be updated to use this new JSDTStructuredContentAssistProcessor when the given partition type is a Javascript partition type, else each processor calls into their super #getContentAssistProcessors. I did have to add an exported package to org.eclipse.wst.jsdt.web.ui to put the new JSDTStructuredContentAssistProcessor in so that JSDTStructuredTextViewerConfigurationJSP could access it. No real way to JUnit this but have tested it manually in both JSPs and HTML pages.
Checked into 3.2.3 and HEAD.