8000 feat(android): fit tab resource icon size based on spec by MartoYankov · Pull Request #7737 · NativeScript/NativeScript · GitHub
[go: up one dir, main page]

Skip to content

feat(android): fit tab resource icon size based on spec #7737

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

Merged
merged 1 commit into from
Aug 28, 2019

Conversation

MartoYankov
Copy link
Contributor
@MartoYankov MartoYankov commented Aug 27, 2019

In order to have the fit to spec tab icons, we need to remove this optimization.

Fixes #7713

@MartoYankov MartoYankov self-assigned this Aug 27, 2019
@cla-bot cla-bot bot added the cla: yes label Aug 27, 2019
@MartoYankov MartoYankov changed the title feat(android): fix tab resource icon size based on spec feat(android): fit tab resource icon size based on spec Aug 27, 2019
@MartoYankov
Copy link
Contributor Author

test nativescript-dev-webpack#next

@MartoYankov MartoYankov merged commit f436b6f into release Aug 28, 2019
@MartoYankov MartoYankov deleted the myankov/fix-tab-res-icons branch August 28, 2019 10:41
manoldonev added a commit that referenced this pull request Sep 12, 2019
* feat(android): fix tab resource icon size based on spec (#7737)

* feat(ios): add icon rendering mode for bottom navigation (#7738)

* fix(ios-tabs): crash when add tabstrip in loaded event (#7743)

* fix(css): parse css selectors with escape sequences (#7689) (#7732)

* fix(ios-tabs): handle nesting proxy view container (#7755)

* fix-next(css): className to preserve root views classes (#7725)

* docs: cut the 6.1.0 release (#7773)

* fix(android-list-picker): NoSuchFieldException on api29 (#7790)

* chore: hardcode tslib version to 1.10.0 (#7776)

* fix(css-calc): reduce_css_calc_1.default is not a function (#7787) (#7801)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0