Thanks for your attention to this! The post above suggest "legacy" as a replacement. I wonder if "backwards-compatible" would be more appropriate for some of our usages?
Bug 1643799 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for your attention to this! The post above suggest "legacy" as a replacement. I wonder if "backwards-compatible" would be more appropriate for some of our usages? Edit: I realized "grandfathered" describes the object while "backwards-compatible" describes the subject, so comments would need to be reworded for that replacement to work. For variables that are named "grandfathered" e.g. referring to a CSS spec, "legacy" may work better, though it's a bit more vague.
Thanks for your attention to this! The post above suggest "legacy" as a replacement. I wonder if "backwards-compatible" would be more appropriate for some of our usages? Edit: I realized "grandfathered" describes the object while "backwards-compatible" describes the subject, so sentences would need to be reworded for that replacement to work. For variables that are named "grandfathered" e.g. referring to a CSS spec, "legacy" may work better, though it's a bit more vague.