Fairy Stockfish 14+ HCE error
ReferenceError: structuredClone is not defined
Opera android.
Replacing the engine doesn't help. Reducing the parameters will not help. It started a long time ago and continues.
Fairy Stockfish 14+ HCE error
ReferenceError: structuredClone is not defined
Opera android.
Replacing the engine doesn't help. Reducing the parameters will not help. It started a long time ago and continues.
@RemRus said ^
Fairy Stockfish 14+ HCE error
ReferenceError: structuredClone is not defined
Opera android.
Replacing the engine doesn't help. Reducing the parameters will not help. It started a long time ago and continues.
Thanks for the report. What Opera version are you running?
@RemRus said [^](/forum/redirect/post/F8QH3DXz)
> Fairy Stockfish 14+ HCE error
> ReferenceError: structuredClone is not defined
>
> Opera android.
> Replacing the engine doesn't help. Reducing the parameters will not help. It started a long time ago and continues.
Thanks for the report. What Opera version are you running?
Knock on wood, but it looks like upgrading to Opera version 68 or higher should resolve this.
Knock on wood, but it looks like upgrading to Opera version 68 or higher should resolve this.
@gamblej said ^
Opera version
66.6.3445
@gamblej said [^](/forum/redirect/post/B2cRGyA2)
> Opera version
66.6.3445
@gamblej said ^
Knock on wood, but it looks like upgrading to Opera version 68 or higher should resolve this.
Is hard with old Android to upgrade
@gamblej said [^](/forum/redirect/post/pYDZJCLP)
> Knock on wood, but it looks like upgrading to Opera version 68 or higher should resolve this.
Is hard with old Android to upgrade
I am aware there is sideloading involved, but it's a one time process. If RemRus is NOT hardware locked on android 5, then opera 68 will get their engine working again. If they ARE stuck on android 5, Firefox maintains support for that up into the 140s. Anything above Firefox 94 should be compatible with the browser engine.
I am aware there is sideloading involved, but it's a one time process. If RemRus is NOT hardware locked on android 5, then opera 68 will get their engine working again. If they ARE stuck on android 5, Firefox maintains support for that up into the 140s. Anything above Firefox 94 should be compatible with the browser engine.
It's been fixed today. Ty for getting lichess back to 100% even on Android 5.
One last peevee, the search time slider doesn't go beyond 30s which seems to be related to the old browser version.
It's been fixed today. Ty for getting lichess back to 100% even on Android 5.
One last peevee, the search time slider doesn't go beyond 30s which seems to be related to the old browser version.
Yes, the search time slider doesn't show ticks at 60s, 120, 300s, and Infinite if Lichess thinks you're on a mobile device.
Using your finger to choose the right value on a slider gets harder with additional ticks. And most people on phones don't want to kill their battery with long or open ended searches, so it's a two birds, one stone kind of thing.
Yes, the search time slider doesn't show ticks at 60s, 120, 300s, and Infinite if Lichess thinks you're on a mobile device.
Using your finger to choose the right value on a slider gets harder with additional ticks. And most people on phones don't want to kill their battery with long or open ended searches, so it's a two birds, one stone kind of thing.
<Comment deleted by user>
@gamblej said ^
Yes, the search time slider doesn't show ticks at 60s, 120, 300s, and Infinite if Lichess thinks you're on a mobile device.
Very helpful info thank you, got paranoid about browser compatibility ha ha
@gamblej said [^](/forum/redirect/post/0FBV1l5j)
> Yes, the search time slider doesn't show ticks at 60s, 120, 300s, and Infinite if Lichess thinks you're on a mobile device.
Very helpful info thank you, got paranoid about browser compatibility ha ha