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 11264: Fix 'android:back' for tabgroup #3237
Conversation
@joshthecoder may have a better approach for this ticket, so I'm going to hold off on reviewing. |
@@ -56,6 +56,7 @@ public View getContentView() { | |||
Activity tabGroupActivity = ((TabProxy) proxy).getTabGroup().getActivity(); | |||
contentView.setActivity(tabGroupActivity); | |||
|
|||
contentView.getKrollObject().setProxySupport(contentView); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should leave a comment here on what we're doing here, like all other setup stuff we do in this method.
Code reviewed, left several comments. |
if (event.getAction() == KeyEvent.ACTION_UP) { | ||
window.fireEvent("android:back", null); | ||
window.fireEvent(backEvent, null); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should fire the event only onto the activity. Then forward listeners on the window to the activity proxy in window.js.
Code reviewed and functionally tested. Request Accepted |
Timob 11264: Fix 'android:back' for tabgroup
testing steps in JIRA: http://jira.appcelerator.org/browse/TIMOB-11264