On Thursday, November 19, 2015 at 1:53:04 PM UTC-8, Andrew Sutherland wrote: > On 11/19/2015 04:39 PM, [email protected] wrote: > > 1) No l10n on back-end. All l10n on front-end[0]. > > [0] Exceptions may exist, they are rare. You case is probably not one of > > them. When in doubt, ni? me or stas :) > > What's the plan for this and service-workers? Specifically, > background-y APIs are all moving to targeting service workers, replacing > our system message mechanism that wakes up content pages directly.
I don't know! Let's find out together. I believe that it's an uncharted territory that we have to yet discover. My naive guess here is that we should think of code that "sends" data to third-party services like notifications/alarms etc. should handle l10n the same way as front-end does. I'm a bit afraid of getting this mingled with real back-end and ending up with back-end that resolves localization strings because they need them for notifications but then, slowly expands to store localized strings for its front-end as well, so I'd love to see this back-end "front-end" code that sends notifications and alarms somehow isolated, but unless there's other reason to do that, we'll have to just be mindful. :) zb. _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
