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 May 11, 2020. It is now read-only.
Openwapp's own emoji support may be removed, as Firefox OS 2.6 natively supports emoji, to reduce code complexity and better integrate Openwapp with the OS.
This is clearly not happening any time soon, as most Firefox OS's (and thus Openwapp's) users are running old Firefox OS versions which have no emoji support. Would it be feasible to create two versions of Openwapp, one retaining compatibility with FxOS 1.3 and the other made for current FxOS versions?
The text was updated successfully, but these errors were encountered:
not, I don't think it's a feasible option. Just because we need two different apps, which will need two different zips. What would happen if the user using 1.3 changes to 2.6+ and has now native emoji? Should we warn them to uninstall its current app (with conversations and preferences) and then install a new one? (without conversations?)
Maybe checking if the user is on 2.6 and has emoji support (is there a flag we can check under document or navigation to see about this feature?) and disable our own emoji keyboard might work, but really low priority, as the future of FxOS is for phones.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Openwapp's own emoji support may be removed, as Firefox OS 2.6 natively supports emoji, to reduce code complexity and better integrate Openwapp with the OS.
This is clearly not happening any time soon, as most Firefox OS's (and thus Openwapp's) users are running old Firefox OS versions which have no emoji support. Would it be feasible to create two versions of Openwapp, one retaining compatibility with FxOS 1.3 and the other made for current FxOS versions?
The text was updated successfully, but these errors were encountered: