This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 234875 - Support for custom HTML tags
Summary: Support for custom HTML tags
Status: NEW
Alias: None
Product: web
Classification: Unclassified
Component: HTML Editor (show other bugs)
Version: 7.4
Hardware: PC Linux
: P1 normal (vote)
Assignee: Milutin Kristofic
Depends on:
Blocks: 234990 235150
  Show dependency tree
Reported: 2013-08-23 12:29 UTC by digitman222
Modified: 2014-10-06 13:26 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description digitman222 2013-08-23 12:29:40 UTC
Would it be possible to add support for custom tags to HTML autocomplete? For example, if someone makes a directive using angularJS, it would be very helpful if that tag would appear in autocomplete. For example, if I made an <uploader> directive, with an attribute called 'url', then I could type 

<uploader u

and it would show 'url' in the autocomplete automatically.

It doesn't have to do this by parsing the angularJS directive code, if there were a way to just specify the custom tags and their attributes manually, that would be just fine.

Comment 1 Petr Pisl 2013-08-23 13:56:21 UTC
I was thinking about this. Not just for html. I would prefer a way that there will be common "format" and way/ui how to specify this for different languages rather than every editor has this implemented in it's way.
Comment 2 digitman222 2013-08-23 16:49:36 UTC
Isn't it only the HTML editor which needs tags and attributes in autocomplete?
Comment 3 Marek Fukala 2013-08-26 07:24:43 UTC
I think there's already an enhancement somewhere for adding a support for injecting custom element's/attributes to the html editor support. I believe this is quite important issue.
Comment 4 Marek Fukala 2013-08-28 12:31:57 UTC
Making this issue bit more generic so it covers the whole editing area, not just the completion.

What'd be nice to have:
1) add an unknown element to a user dictionary
2) add an unknown attribute of un/known element to a user dictionary
3) edit the dictionary file which has some appropriate format
4) completion then takes the dictionary into account
5) define content type of an element's content 
6) define content type of an attribute's content
note: effect of 5,6 is that a lexical/parser embedding is created for such elements/attrs so some editing features can be available for them (if implemented).
Comment 5 Petr Pisl 2013-12-17 14:14:19 UTC
Not implemented in NB 8.0