Open Bug 1910843 Opened 1 year ago Updated 1 year ago

Migrate Accessible::TranslateString to nsContentUtils::FormatLocalizedString

Categories

(Core :: Disability Access APIs, enhancement)

Product:
Core
Component:
Disability Access APIs
Type:
enhancement

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: vhilla, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0

Blocks: cleana11y

I noticed in Bug 1694789 that localized strings from dom/locales/en-US/chrome/accessibility/*/accessible.properties are not available via nsContentUtils::FormatLocalizedString. To my knowledge, this is the function usually used for localization. Instead, Accessible::TranslateString is used, which provides less functionality.

I think this should be easy to migrate, just add chrome://global-platform/locale/accessible.properties (as used here) to gPropertiesFiles here and to PropertiesFile enum here, then change the currently 2 (3 with my patch from Bug 1694789) usages of TranslateString.

You need to log in before you can comment on or make changes to this bug.