| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
test ios#/tns-dist/tns-ios/PR/e34f49eb5af64946cf1257bd2b39760518235427/tns-ios.tgz |
Sorry, something went wrong.
| } else if (item.icon) { | ||
| const img = loadActionIconFromFileOrResource(item.icon); | ||
| barButtonItem = UIBarButtonItem.alloc().initWithImageStyleTargetAction(img, UIBarButtonItemStyle.Plain, tapHandler, "tap"); | ||
| const image = img.imageWithRenderingMode(this._getIconRenderingMode()); |
There was a problem hiding this comment.
Guard the img usage as here
?
Sorry, something went wrong.
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Checklist
What is the current behavior?
On Android, icons rendered in TabView and Actionbar are not scaled correctly due to the use of a deprecated native Android constructor https://developer.android.com/reference/android/graphics/drawable/BitmapDrawable#BitmapDrawable(android.graphics.Bitmap).
On iOS, there was no property on ActionBar to specify icon rendering mode and it is hard coded to alwaysOriginal, which made the use of image icons limited.
What is the new behavior?
Fixed the Android issue with the use of the new constructor.
Added iosIconRenderingMode on ActionBar. To avoid breaking changes, on ActionBar this property defaults to alwaysOriginal and on TabView, it defaults to automatic. We should probably change this for 6.0.
Fixes #5887
Tests