Somangshu Goswami

I dont see why we need another widget? Seems like a lot of work for the end user if they have to just add a onClick action on a pre-existing...

Understood, I think if the button is getting clicked we should only fine the button onClick event, The onus would be on the user. We will only follow the basic...

Seem like the way we have implemented this is the challenge, A password field does not expose the value attribute in html source. But since we are all converting this...

## Stats | Stat | Values | | ------------- | ------------- | | Reach | 263 | | Effort (months) | 0.5 |

@dilippitchika the problem I think is with the html element in the source showing the password value. Not a web standard. The user explicitly taking the action to see it...

@dilippitchika Short answer: this is a bug. This is an implementation challenge, should be fixed internally, we dont need any additional property or config here

@AthiraVijayan21 thanks for commenting here. This is not yet prioritised, we have not yet figured out the right solution for this cc @dilippitchika

@keyurparalkar would you be able to take this up in the current sprint?

@dilippitchika mentioned that point 1 is important cc @momcilo-appsmith

@dhruvikn kindly leave the discussed next steps here!