You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Border radius is not working on Android API 17 #1000
@vakrilov - is there a negative performance impact by using this on images? What about buttons? Border-radius doesnt work on my device (issue ref above) so wondering if the same internal canvas code is used on buttons? Thanks!
@bradmartin
There might a negative performance impact - for example if rounded borders are used on many elements on a page - please refer to hardware acceleration article. However, keep in mind that:
This fix forces software layer only if android API level is below 18 (which means - only 17 as it is a minimum supported by native-script)
Software layer is used only for views that have rounded corners - so it won't impact other elements.
About the Canvas API-s we are using - you can check them here. Probably the canvas.clipPath(path) call was causing the issue with rendering - according to the article above it is supported on after API lvl 18.
Activity
vchimev commentedon Oct 30, 2015
Hi @lscown,
We managed to reproduce the issue and will look into it.
vakrilov commentedon Nov 9, 2015
It look like some of the canvas APIs (forexample
canvas.clipPath(path)) we are using are unsupported if hardware accelerations is enabled.The solution is to use software layer for the view:
bradmartin commentedon Nov 10, 2015
@vakrilov - is there a negative performance impact by using this on images? What about buttons? Border-radius doesnt work on my device (issue ref above) so wondering if the same internal canvas code is used on buttons? Thanks!
vakrilov commentedon Nov 10, 2015
@bradmartin
There might a negative performance impact - for example if rounded borders are used on many elements on a page - please refer to hardware acceleration article. However, keep in mind that:
About the Canvas API-s we are using - you can check them here. Probably the
canvas.clipPath(path)call was causing the issue with rendering - according to the article above it is supported on after API lvl 18.lock commentedon Aug 30, 2019
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.