Closed Bug 1548777 Opened 5 years ago Closed 5 years ago

Add support for Fluent to firefox-puppeteer

Categories

(Remote Protocol :: Marionette, enhancement, P3)

Version 3
enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: whimboo, Unassigned)

References

Details

(Keywords: pi-marionette-firefox-puppeteer)

The l10n team is moving forward pretty quickly in converting more and more windows and dialogs of Firefox from DTD/property style definitions to Fluent. As such we should add support for it.

Please note that Fluent asynchronously fetches the information based on some observers / window load status.

Axel and Francesco, would you mind giving me a bit more information in how it works, and which options we could use to hook into the system to retrieve localized text? Thanks

Flags: needinfo?(l10n)
Flags: needinfo?(francesco.lodolo)
Type: defect → enhancement

I think you're looking for https://firefox-source-docs.mozilla.org/intl/l10n/l10n/fluent_tutorial.html#non-markup-localization.

This only works for XUL/HTML, but not for fluent-react, like in parts of devtools. I don't know of an option there, tbh.

Flags: needinfo?(l10n)
Flags: needinfo?(francesco.lodolo)

Thanks. I will have a look at when I find the time. Until then we might have to skip specific tests.

Sadly this bug has lower priority for us at the moment. I cannot tell when I will be able to work on it. If there is a more urgent situation for you to get this implemented please let us know.

Priority: -- → P3

I chatted with Axel in person yesterday, and told there are no plans for specific l10n tests in the near future. I also explained that this package will go away, and will have to find a proper replacement in the future. Maybe foxpuppet via Selenium could handle that in the future, but it would be a totally different project.

As long as the firefox ui tests with specific l10n text assertions exist, we will have to disable certain assertions.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.