(In reply to Adam Gashlin (he/him) [:agashlin] from comment #18) > It seems possible to add a newline to a button by using CR or LF (` ` or ` `) in the content string, at least in my playing around with [Notifications Visualizer](https://docs.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/notifications-visualizer). This would be awkward for localization but should at least make it possible to use longer strings. Unfortunately I don't think *awkward* describes the situation accurately. This would be incredibly error prone: - Someone needs to test it, and realize that they need a new line. Otherwise they'll ship a button that doesn't make any sense for the user. - Add a new line with a format that is not used anywhere else in the codebase (`\n` is normally used in these case, and that's still confusing). One the first point, a couple of examples (guessing what German and French could try to use): - Italian: `Imposta Firefox come browser predefinito…` would likely show up as the equivalent of `Make Firefox as b` - German: (guessing) `Firefox als Standardbrowser festlegen` -> `Firefox als Standardbro` (`Firefox as standardwhat??`, no verb) - French: (guessin) `Faire de %S mon navigateur par défaut` -> `Faire de Firefox mon ` (`Make Firefox my`) That doesn't scale for 96 languages, or even for the ones we care more about, given there's no testing automation (e.g. automated screenshots).
Bug 1621696 Comment 20 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Adam Gashlin (he/him) [:agashlin] from comment #18) > It seems possible to add a newline to a button by using CR or LF (` ` or ` `) in the content string, at least in my playing around with [Notifications Visualizer](https://docs.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/notifications-visualizer). This would be awkward for localization but should at least make it possible to use longer strings. Unfortunately I don't think *awkward* describes the situation accurately. This would be incredibly error prone: - Someone needs to test it, and realize that they need a new line. Otherwise they'll ship a button that doesn't make any sense for the user. - Add a new line with a format that is not used anywhere else in the codebase (`\n` is normally used in these case, and that's still confusing). One the first point, a couple of examples (guessing what German and French could try to use): - Italian: `Imposta Firefox come browser predefinito…` would likely show up as the equivalent of `Make Firefox as b` - German: (guessing) `Firefox als Standardbrowser festlegen` -> `Firefox als Standardbro` (`Firefox as standardwhat??`, no verb) - French: (guessin) `Faire de Firefox mon navigateur par défaut` -> `Faire de Firefox mon ` (`Make Firefox my`) That doesn't scale for 96 languages, or even for the ones we care more about, given there's no testing automation (e.g. automated screenshots).