You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Jesse MacFadyen (JIRA)" <ji...@apache.org> on 2016/09/09 18:37:20 UTC

[jira] [Resolved] (CB-11281) Prompt dialog: defaultText is not taken as input if no input by user

     [ https://issues.apache.org/jira/browse/CB-11281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesse MacFadyen resolved CB-11281.
----------------------------------
    Resolution: Fixed

> Prompt dialog: defaultText is not taken as input if no input by user
> --------------------------------------------------------------------
>
>                 Key: CB-11281
>                 URL: https://issues.apache.org/jira/browse/CB-11281
>             Project: Apache Cordova
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Plugin Dialogs
>    Affects Versions: 3.5.0
>         Environment: Windows 10
>            Reporter: Kai Schätzl
>            Assignee: Deshan Kalupahana
>            Priority: Minor
>              Labels: Windows, easy, easyfix, triaged, windows-universal
>             Fix For: Master
>
>
> Consider the case where you have a defaultText for navigator.notification.prompt, the user sees it and then hits enter.
> With the original Javascript prompt dialog you get whatever's in the field as output. var result = prompt ("Description", "Default Value");
> So, if the user enters nothing you get the default value given as your value in result.
> This is the expected behavior when mimicking this dialog.
> To my surprise, this is not what happens with navigator.notification.prompt. If the user enters nothing then nothing is returned via results.input1. Although it looks like something is already "sitting" there and waiting for submit.
> I think this behavior should be changed according to what the Javascript prompt dialog does. That makes it consistent with browser behavior and what most people expect.
> This bug might be related to https://issues.apache.org/jira/browse/CB-11214, where the reporter seems to expect the opposite (not sure about that).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org