Thank you for the input, Emilio. I think that's a reasonable perspective, and given that Jamie has expressed, "at the end of the day, I could live with either solution," I'm inclined to follow your guidance here. It would be a lot easier to justify shipping the feature with saying "Translation complete" and improving upon that behavior in the future, compared to implementing a hack to achieve the optimal experience on release with the worry of surprise regressions from seemingly out of nowhere. I'm grateful for all of the discussion above, and I feel that the reasoning behind the decision is well documented. I will be filing a follow-up bug to continue investigating a better way to announce the text automatically, and I will link to it in the comments next to the `a11yUtils.announce` call.
Bug 1894091 Comment 17 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thank you for the input, Emilio. I think that's a reasonable perspective, and given that Jamie has expressed, "at the end of the day, I could live with either solution," I'm inclined to follow your guidance here. It would be a lot easier to justify shipping the feature with saying "Translation complete" and improving upon that behavior in the future, compared to implementing a hack to achieve the optimal experience on release with the worry of surprise regressions from seemingly out of nowhere. I'm grateful for all of the discussion above, and I feel that the reasoning behind the decision is well documented. I will be filing a follow-up bug to continue investigating a better way to announce the text automatically, and I will link to it in the comments next to the `a11yUtils.announce` call. --- Morgan, given the final decision here to utilize `a11yUtils.announce` I would appreciate you putting Bug 1888310 back on your radar at your earliest convenience. And please let me know if there is anything I can do to help with that fix.
Thank you for the input, Emilio. I think that's a reasonable perspective, and given that Jamie has expressed, "at the end of the day, I could live with either solution," I'm inclined to follow your guidance here. It would be a lot easier to justify shipping the feature with saying "Translation complete" and improving upon that behavior in the future, compared to implementing a hack to achieve the optimal experience on release with the worry of surprise regressions from seemingly out of nowhere. I'm grateful for all of the discussion above, and I feel that the reasoning behind the decision is well documented. I will be filing a follow-up bug to continue investigating a better way to announce the text automatically, and I will link to it in the comments next to the `a11yUtils.announce` call. --- Morgan, given the final decision here to utilize `a11yUtils.announce` I would appreciate you putting Bug 1888310 back on your radar at your earliest convenience. And please let me know if there is anything I can do to help with that fix. (Sending you a NI for the sake of notifying you about the decision. Feel free to clear it, no response needed.)