Fixed
Status Update
No update yet.
Comments
tj...@gmail.com
The problem is very serious.
Currently html5 clearRect isn't working within any android 4 devices.
Please, solve this problem as soon as possible.
Currently html5 clearRect isn't working within any android 4 devices.
Please, solve this problem as soon as possible.
te...@gmail.com
we have the same problem
We are waiting for a patch since November because none of the workaround we have tried is stable.
We hope that the patch will come before the launching of our app and if not...well, sadly, we will launch the app on iOS and windows only
We are waiting for a patch since November because none of the workaround we have tried is stable.
We hope that the patch will come before the launching of our app and if not...well, sadly, we will launch the app on iOS and windows only
st...@gmail.com
[Comment deleted]
da...@gmail.com
Still appears to be an issue as I'm getting quirky results when trying clearRect in a loop. #3 solution is good but too heavy to work in a loop.
wh...@gmail.com
What about using requestAnimationFrame for loop rather than using a timer loop ?
il...@google.com
fl...@gmail.com
Hey, this is a serious issue that is affecting our production components, could someone please look into this???
jo...@onsalesit.com
is there any solvtion for that issue ?
dj...@gmail.com
Something like that works for me:
function bug_workaround() {
$(canvas).hide();
setTimeout(function() {
$(canvas).show();
}, 1);
}
I call this function after clear.
function bug_workaround() {
$(canvas).hide();
setTimeout(function() {
$(canvas).show();
}, 1);
}
I call this function after clear.
mo...@google.com
mo...@google.com
Opacity trick is better because will not initiate page reflow and hide /
show will.
show will.
ra...@gmail.com
which trick would that be? modify the opacity?
mo...@google.com
Yes,
function bug_workaround() {
canvas.style.opacity = 0.99;
setTimeout(function() {
canvas.style.opacity = 1;
}, 1);
}
function bug_workaround() {
canvas.style.opacity = 0.99;
setTimeout(function() {
canvas.style.opacity = 1;
}, 1);
}
kk...@google.com
[Comment deleted]
al...@gmail.com
Hi,
I'm having the same problem but the workaround doesn't seem to help. Was wondering if this issue is somehow fixed by now?
Thank You.
I'm having the same problem but the workaround doesn't seem to help. Was wondering if this issue is somehow fixed by now?
Thank You.
Description
Version used: 27.1.0
Theme used: AppCompat No ActionBar
Devices/Android versions reproduced on:
I currently use a base fragment transaction with the following code to animate fragment replacements by default from within a support fragment:
getFragmentManager()
.beginTransaction()
.setCustomAnimations(android.R.anim.fade_in, android.R.anim.fade_out, android.R.anim.fade_in, android.R.anim.fade_out);
This worked great on Support library version 27.0.2 and below. Version 27.1.0 however causes the replaced fragment to flicker for a second or so after the new fragment is shown.
The fragment transactions do NOT have setReorderingAllowed to true, NOR do they postpone any pending transitions.