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
When we try to use Clapper in the last version of Firefox (and macOS but I suspect other platforms as well),
the Clapper wbe app will crash after a few seconds of trying to use the timeline
(like, literally - the page tab disappear instantly, without any error message)
Notes
In my humble opinion, this is a Firefox bug, not a Clapper bug. No application is supposed to "crash", at the least it should display an error message in the browser console logs.
(I mean, Clapper even works decently on browsers with more limitations such as Safari Mobile, so.. 🤷 )
It's also not the fault of of tech decision of using WebGL, we are not going back on this (Figma uses WebGL as well, and everybody loves Figma)
Solution
Let's see if there are some quickwins we can do to try to improve compatibility with Firefox.
But let's not spend too much time of this since we are going to have a better alternative: a Desktop app.
The text was updated successfully, but these errors were encountered:
Context
When we try to use Clapper in the last version of Firefox (and macOS but I suspect other platforms as well),
the Clapper wbe app will crash after a few seconds of trying to use the timeline
(like, literally - the page tab disappear instantly, without any error message)
Notes
In my humble opinion, this is a Firefox bug, not a Clapper bug. No application is supposed to "crash", at the least it should display an error message in the browser console logs.
(I mean, Clapper even works decently on browsers with more limitations such as Safari Mobile, so.. 🤷 )
It's also not the fault of of tech decision of using WebGL, we are not going back on this (Figma uses WebGL as well, and everybody loves Figma)
Solution
Let's see if there are some quickwins we can do to try to improve compatibility with Firefox.
But let's not spend too much time of this since we are going to have a better alternative: a Desktop app.
The text was updated successfully, but these errors were encountered: