Community
Participate
Working Groups
Build Identifier: 20100527-0614 When setting the content type property of proposal computer and using the plugin editor to find the content type it sets the value to the short id instead of full id which then makes the extension not work. Example: Instead of <contentType id="org.eclipse.wst.html.core.htmlsource"> it's just set to <contentType id="htmlsource"> Reproducible: Always Steps to Reproduce: 1. Create new plugin project 2. Through plugin editor add org.eclipse.wst.sse.ui.completionProposal 3. Add some content type to the extension (htmlsource is easy to test) 4. Add a class providing the extension and just put a break point in the begining of computeCompletionProposals() 5. Run the plugin in debug mode and triger content assist in a html page, if the breakpoint is not triggered the issue is valid
We can, and should, now use a fully qualified ID value when declaring our content types.
Fixed in M1 for JS, XML, XSD, HTML, DTD, CSS, and JSP-contributed content types.