Agreed. This is probably a side-effect of an upstream cross-browser patch in webL10n.