(In reply to Dianna Smith [:diannaS] from comment #2) > is this actually a p1/s1? not sure this needs to be tracked for 138 Bug 1949847 did land only one day ago on 139, and so this would have not been tracked for 138, the know issue is actually we are fixing is mainly related to Thunderbird, but given that they would not be able to have the default en-US dictionary if we don't fix it on the I marked it as P1 to signal that this is something we want to take care of right away in the same Gecko version that has introduced the issue. Setting S1 was actually done by mistake, given that I set "task" on this ticket because the change that introduced the issue for Thunderbird builds is still nightly only and wasn't yet riding the train (and so I'm setting severity as N/A along with this bugzilla comment).
Bug 1961356 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Dianna Smith [:diannaS] from comment #2) > is this actually a p1/s1? not sure this needs to be tracked for 138 Bug 1949847 did land only one day ago on 139, and so this would have not been tracked for 138, the know issue that we are actually fixing is mainly related to Thunderbird, but given that they would not be able to have the default en-US dictionary if we don't fix it on the I marked it as P1 to signal that this is something we want to take care of right away in the same Gecko version that has introduced the issue. Setting S1 was actually done by mistake, given that I set "task" on this ticket because the change that introduced the issue for Thunderbird builds is still nightly only and wasn't yet riding the train (and so I'm setting severity as N/A along with this bugzilla comment).
(In reply to Dianna Smith [:diannaS] from comment #2) > is this actually a p1/s1? not sure this needs to be tracked for 138 Bug 1949847 did land only one day ago on 139, and so this would have not been tracked for 138, the know issue that we are actually fixing is mainly related to Thunderbird, but given that they would not be able to have the default en-US dictionary if we don't fix it on the Gecko side I marked it as P1 to signal that this is something we want to take care of right away in the same Gecko version that has introduced the issue. Setting S1 was actually done by mistake, given that I set "task" on this ticket because the change that introduced the issue for Thunderbird builds is still nightly only and wasn't yet riding the train (and so I'm setting severity as N/A along with this bugzilla comment).