Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WPF: Switching secureTextEntry on TextInput removes value #1935

Closed
acuntex opened this issue Aug 10, 2018 · 1 comment
Closed

WPF: Switching secureTextEntry on TextInput removes value #1935

acuntex opened this issue Aug 10, 2018 · 1 comment

Comments

@acuntex
Copy link

acuntex commented Aug 10, 2018

Environment

  1. react-native -v:
    react-native-cli: 2.0.1
    react-native: 0.55.4
  2. npm ls rnpm-plugin-windows:
    `-- [email protected]
  3. npm ls react-native-windows:
    `-- [email protected] (github:Microsoft/react-native-windows)
  4. node -v:
    v10.3.0
  5. npm -v:
    6.1.0

Then, specify:

  • Target Platform:
    WPF

  • Target Platform Version(s):
    .NET 4.6.1

  • Target Device(s):
    Desktop

  • Development Operating System:
    Windows

  • Visual Studio Version:
    Visual Studio 2017

  • Build Configuration:
    Debug, DebugBundle, Release, ReleaseBundle

Steps to Reproduce

Create a TextInput field which is able to switch the secureTextEntry-flag ("Show password button e.g.").

                    <View style={{height: 100}}>
                        <TextInput style={{height: 50, color: "black"}} secureTextEntry={!this.state.passwordVisible}/>
                        <TouchableOpacity onPress={() => { this.setState({passwordVisible: !this.state.passwordVisible}); }}>
                            <Text>Change Visibility</Text>
                        </TouchableOpacity>
                    </View>

Expected Behavior

When changing secureTextEntry the TextInput should not loose the value.

Actual Behavior

When changing secureTextEntry the TextInput should looses the value.

@chrisglein chrisglein added the .NET Archive Issue opened against deprecated .NET implementation, will be closed (label drives bot activity) label Oct 25, 2019
@ghost
Copy link

ghost commented Oct 25, 2019

We are not investing in new features or lower priority bug fixes on vCurrent. The bulk of investment is now in vNext as we prepare to make that the default choice. If this issue is still relevant on the vNext implementation please open a vNext issue. If this issue is of significant severity for a vCurrent app and vNext is not an option, re-open with justification.

@ghost ghost removed the .NET Archive Issue opened against deprecated .NET implementation, will be closed (label drives bot activity) label Oct 25, 2019
@chrisglein chrisglein added the .NET Archive Issue opened against deprecated .NET implementation, will be closed (label drives bot activity) label Oct 25, 2019
@ghost ghost removed the .NET Archive Issue opened against deprecated .NET implementation, will be closed (label drives bot activity) label Oct 25, 2019
@ghost ghost closed this as completed Oct 25, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants