-
7 May 2012 6:23 AM #1
Ext.device.Notification.Simulator.show disappears under Ext.Panel (z-index problem)
Ext.device.Notification.Simulator.show disappears under Ext.Panel (z-index problem)
If you call Ext.MessageBox.show directly you can use the zIndex option. However, if you use Ext.device.Notification.show - which relays to Ext.device.notification.Simulator when not packed as native app - you cannot and the z-index always has the default value of 10.
If you call Ext.device.Notification.show from a (floating) Ext.Panel and/or after some Ext.NavigationView.push() call's, the z-index will be lower then the Ext.Panel and the dialog will disappear under the Ext.Panel and will be invisible and unclickable.
Probably this is not a huge problem since you'll only call Ext.MessageBox.show through Ext.device.Notification.show if you're releasing the app as a native app, which will use Ext.device.Notification.Sencha or PhoneGap anyway.
Possible solution:
Ext.device.Notification.Simulator could find the highest z-index and pass it (+ 1) to Ext.device.Notification.show, or just pass 9999 all the time
-
7 May 2012 1:25 PM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,624
- Vote Rating
- 434
Thank you for the report.
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
14 May 2012 2:09 PM #3
Fixed for the next release. Thank you!
Sencha Inc.
Robert Dougan - @rdougan
Sencha Touch 2 and Ext JS 4 Core Team Member, SASS/Theming Wizard.
Success! Looks like we've fixed this one. According to our records the fix was applied for
TOUCH-2888
in
Sprint 22 (2.0.2).


Reply With Quote