Community
Participate
Working Groups
Build Identifier: I20100608-0911 When changing the read-write property of file to be read-only, the StructuredTextViewer de-configures (uninstalls) the ContentAssistant, which in its turn releases the ContentAssistProcessors (loaded on Viewer's initialization). From this moment if you try to set up the file to be read-only the Editor Content Assistant will be installed with no initial CA-processors and there will be no normal content assistant. Reproducible: Always Steps to Reproduce: 1. Open a writable html or jsp page in editor and try to use CA facility 2. From the Package Explorer change the file properties to make it read-only. 3. Try to invoke CA again (As result it will be invoked before the editor state validation occurrence - FAIL) 4. Try to insert some CA proposal (As result the selected proposal will be applied and editor state will be changed to "modified" - FAIL) 5. Try to press Ctrl-Z or type some character. As result "Read-only File Encountered" dialog will be displayed due to suggest to make file to be writable. Press "Yes". 6. Try to use Content Assist. (FAIL) It will not be shown until you close the editor and then open it again on the same file.
Sorry, please read the following: "From this moment if you try to set up the file to be read-only" in description as "From this moment if you try to set up the file to be WRITABLE".
Hi, Victor. Please upgrade to Helios SR2. This was fixed in Bug 281872. *** This bug has been marked as a duplicate of bug 281872 ***