Github user Ramakrishnan-V commented on the issue:
https://github.com/apache/nifi/pull/1546
Hi @mcgilman,
I strongly agree on your point that need to introduce new attribute of
PropetyDescriptor which would drive whether or not to use a masked single line
input or the existin
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1546
forget it. Seen what @mcgilman was referring to. Possible to play with text
area but it becomes single line. :-(
---
If your project is set up for it, you can reply to this email and have your
reply
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1546
The approach linked above seems to work on chrome without the javascript
but firefox required the js code.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1546
@scottyaslan - have you tested this?
http://jsfiddle.net/Ldr07h2r/6/
Source:
http://stackoverflow.com/questions/25822682/webkit-text-security-compatibility
---
If your project i
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1546
Hey @scottyaslan,
This is a great start, but I think there are a few fundamental issues with
how `PropertyDescriptors` relay what sort of editor should be used. There does
not appear to be a
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1546
Will review...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
