Thanks for taking a look! >we should probably still be able to enable the UI element It is a little complicated because we don't want to enable the UI element on devices that translations is not supported on. On bug 1958042 comment 2, I gave an overview of all the nuance of each of those startup calls. `requestEngineSupport` probably needs to happen extremely early. We can help it out by storing this result somewhere and recalling it, because it shouldn't change. (The engine support is linked to device hardware, but the first time would still need to ask the translations engine in toolkit.)
Bug 1965261 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for taking a look! >we should probably still be able to enable the UI element It is a little complicated because we don't want to enable the UI element on devices that translations is not supported on. On bug 1958042 comment 2, I gave an overview of all the nuance of each of those startup calls. `requestEngineSupport` probably needs to happen extremely early. We can help it out by storing this result somewhere and recalling it, because it shouldn't change. (The engine support is linked to device hardware, but the first time would still need to ask the translations engine in toolkit.) Although, even making the supported engine call early, solving this would still be tricky because a lot of information is retrieved to show in the UI. (Like supported language names, user settings, etc.)
Thanks for taking a look! >we should probably still be able to enable the UI element It is a little complicated because we don't want to enable the UI element on devices that translations is not supported on. On bug 1958042 comment 2, I gave an overview of all the nuance of each of those startup calls. `requestEngineSupport` probably needs to happen extremely early. We can help it out by storing this result somewhere and recalling it, because it shouldn't change. (The engine support is linked to device hardware, but the first time would still need to ask the translations engine in toolkit.) Although, even making the supported engine call early, solving this would still be tricky because a lot of information is retrieved to show in the UI. (Like supported language names, user settings, etc. I tend to think that we'd have the language names by the time the user opened the menu, though.)
Thanks for taking a look! >we should probably still be able to enable the UI element It is a little complicated because we don't want to enable the UI element on devices that translations is not supported on. On bug 1958042 comment 2, I gave an overview of all the nuance of each of those startup calls. `requestEngineSupport` probably needs to happen extremely early. We can help it out by storing this result somewhere and recalling it, because it shouldn't change. (The engine support is linked to device hardware, but the first time would still need to ask the translations engine in toolkit.) Although, even making the supported engine call early, solving this would still be tricky because a lot of information is retrieved to show in the UI. (Like supported language names, user settings, etc. I tend to think that we'd have the language names by the time the user opened the feature, though.)
Thanks for taking a look! >we should probably still be able to enable the UI element It is a little complicated because we don't want to enable the UI element on devices that translations is not supported on. On bug 1958042 comment 2, I gave an overview of all the nuance of each of those startup calls. `requestEngineSupport` probably needs to happen extremely early. We can help it out by storing this result somewhere and recalling it, because it shouldn't change. (The engine support is linked to device hardware, but the first time would still need to ask the translations engine in toolkit.) Although, even making the supported engine call early, solving this would still be tricky because a lot of information is retrieved to show in the UI. (Like supported language names, user settings, etc. I tend to think that we'd have the language names by the time the user opened the feature, though. Assuming we already have the hardware support flag early.)