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

Ext.Net.RadioGroup change event triggers too early #1423

Open
fabriciomurta opened this issue Jan 27, 2017 · 6 comments
Open

Ext.Net.RadioGroup change event triggers too early #1423

fabriciomurta opened this issue Jan 27, 2017 · 6 comments

Comments

@fabriciomurta
Copy link
Contributor

Found: 4.2.0
Ext.NET forum thread: RadioGroup issue
Sencha forum thread: 6.2.1 classic: RadioGroup's change event is fired too early

Ext.Net.RadioGroup's change event triggers too early from client side, in a moment where the component is (even worse) in an inconsistent state of two items selected. The following fiddle shows the issue on pure ExtJS: RadioGroup change event.

Although for most issues we can just use the newValue and oldValue provided to the event, there's a problem that if a direct method is called during the event, the submitted form will reflect the inconsistent selection state of the component, as in the sample code provided for issue #1421.

The error was not reproducible in ExtJS 6.0.2.

@fabriciomurta
Copy link
Contributor Author

Update: Issue still open after ExtJS 6.5.0 release.

@fabriciomurta
Copy link
Contributor Author

Update: Issue still open after ExtJS 6.5.1 release. Issue is acknowledged by Sencha under ID EXTJS-23582.

@fabriciomurta
Copy link
Contributor Author

Update: Issue still open after ExtJS 6.5.2 release. Issue is acknowledged by Sencha under ID EXTJS-23582.

@fabriciomurta
Copy link
Contributor Author

Update: Issue still open after ExtJS 6.5.3 release. Issue is acknowledged by Sencha under ID EXTJS-23582.

@fabriciomurta
Copy link
Contributor Author

Update: Issue still open after ExtJS 6.6.0.258 release. Issue is acknowledged by Sencha under ID EXTJS-23582.

@fabriciomurta
Copy link
Contributor Author

Update: Issue still open after ExtJS 6.7.0.161 release. Issue is acknowledged by Sencha under ID EXTJS-23582.

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

1 participant