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 }}
This repository has been archived by the owner on Jun 15, 2021. It is now read-only.
We have a live environment where users (on relatively recent versions of Firefox, Chrome and Safari) enter rich text via Scribe. It gets used tens of thousands of times each month from Safari without any major hurdles -- we're monitoring client errors with Sentry and applying patches if necessary.
As such, I believe Scribe is pretty much ready for prime time in Safari. Is there anything, with the caveat of adding the necessary polyfills (Object.assign), that would be needed to declare official support (e.g. tests that run against Safari)?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a live environment where users (on relatively recent versions of Firefox, Chrome and Safari) enter rich text via Scribe. It gets used tens of thousands of times each month from Safari without any major hurdles -- we're monitoring client errors with Sentry and applying patches if necessary.
As such, I believe Scribe is pretty much ready for prime time in Safari. Is there anything, with the caveat of adding the necessary polyfills (
Object.assign
), that would be needed to declare official support (e.g. tests that run against Safari)?The text was updated successfully, but these errors were encountered: