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

[timob-16893]: Android update doc and behavior for 'enableReturnKey' property #5741

Merged
merged 1 commit into from Jul 29, 2014

Conversation

hieupham007
Copy link
Contributor

Testing steps in JIRA

@hieupham007 hieupham007 changed the title timob-16893: Update doc and behavior for 'enableReturnKey' property [timob-16893]: Android update doc and behavior for 'enableReturnKey' property May 28, 2014
enableReturnKey = TiConvert.toBoolean(proxy.getProperty(TiC.PROPERTY_ENABLE_RETURN_KEY), false);
}
if (enableReturnKey && v.getText().length() == 0) {
return true;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we do this we can never enter the newline as the first character in TextArea

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is already the case in the current codebase, I only move this check up so we don't fire the return event. I think this is correct behavior since the docs for TextArea says: If true, the return key is disabled when this text area is empty, and automatically enabled as soon as the user types any text in the area.

@vishalduggal
Copy link
Contributor

CR + FR ok. APPROVED

vishalduggal added a commit that referenced this pull request Jul 29, 2014
[timob-16893]: Android update doc and behavior for 'enableReturnKey' property
@vishalduggal vishalduggal merged commit c8c9e43 into tidev:master Jul 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants