Christian Lenz created NETBEANS-1702:
----------------------------------------
Summary: Get rid oft he HTML custom tags check
Key: NETBEANS-1702
URL: https://issues.apache.org/jira/browse/NETBEANS-1702
Project: NetBeans
Issue Type: Wish
Components: web - HTML Editor
Affects Versions: Next
Reporter: Christian Lenz
In the year of 2018, with custom elements around the world, angular, react,
vue, polymer, web components standard, etc. NetBeans should get rid of checking
HTML fles for custom elements. It is often a mess, to see an HTML file with
hints on each element NetBeans doesn't know, to add them manually to the
custom.json file.
I can think of some solutions:
* Make NetBeans possible to let custom elements/web components available by
default. No hints/warnings, no adding to custom.json etc. or maybe adding all
custom/unknown elements to the custom.json per default. Because NetBeans needs
to know them for code completion.
* Make NetBeans possible to let custom elements/web components available by
default but make a hint to go back to the current behaviour to use known HTML
tags and check for custom tags again.
IMHO, there is no need to check for custom elements nowadays anymore. So I
would go with the first proposal.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
