Bugzilla

(In reply to Edouard Oger [:eoger] from comment #10)
> > Why this menu doesn't have an accesskey? Is it expected? If it needs fixing, it needs to land ASAP: I can block exposing other strings for localization for a few hours, otherwise it will need to land with a new ID to fix it. The alternative is asking for a backout.
> 
> I don't mind making a new string ID, do you have an access key suggestion?

So, it does need an accesskey? From a quick look at the tools menu, It looks like `n` is free, but you should double check with an actual English build.

Note that I do mind changing the ID, because we would be asking folks to translate the same label twice within a few days.

(In reply to Edouard Oger [:eoger] from comment #10)
> > Why this menu doesn't have an accesskey? Is it expected? If it needs fixing, it needs to land ASAP: I can block exposing other strings for localization for a few hours, otherwise it will need to land with a new ID to fix it. The alternative is asking for a backout.
> 
> I don't mind making a new string ID, do you have an access key suggestion?

So, it does need an accesskey? From a quick look at the tools menu, It looks like `n` is free, but you should double check with an actual English build.

Note that I do mind changing the ID, because we would be asking folks to translate the same label twice within a few days. If the fix lands before EOD, I can hold on with updating strings, but not for several days.