[ https://issues.jboss.org/browse/JBIDE-18724?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-18724: ----------------------------------------- The fix for the Upstream issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=444545) is split into two separated Core and UI (https://bugs.eclipse.org/bugs/show_bug.cgi?id=448152 is created for the UI part) patches and the only its Core part will be included into WTP 3.6.2 release. As such we have to adapt it locally in JBT. There are number of cases are possible in order to adopt JBT to the upstream fix: 1. Since no UI part will be added to WTP to control the tag name ignorance preferences, we can force the default values (and/or even the actual values) for the Syntax Validator to ignore all the names that match ion-* pattern. No UI is requires with this fix, all the WTP installations are to use these preference values, but it will be impossible to change the preferences. So, the list of tag name patterns is to be carefully defined. 2. The second solution is to create an additional preference page for the WTP Syntax Validator preferences as well as QuickFix that allows to add tag names into ignorance list in JBT's Ionic plug-in. This will give a user the possibility to ignore any tag names on his own. I'd like not force the change of the default/actual values for these preferences because otherwise it will be a behaviour opposite to the WTP one and as such it might confuse the users. WDYT? My +1 is for the case 1. -- This message was sent by Atlassian JIRA (v6.3.1#6329)