Expose Node.can_auto_translate()
#107344
Merged
Expose Node.can_auto_translate()
#107344
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mickeon
reviewed
Jun 10, 2025
timothyqiu
force-pushed
the
can-auto-translate
branch
from
ce79a2a to
4e20e33
Compare
AThousandShips
approved these changes
Jun 11, 2025
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
{Control,Window}.auto_translatehas long been deprecated forNode.auto_translate_mode.However, a substitute for the getter is never provided. This means that we have no easy way to tell whether a node auto translates for nodes that are neither Control nor Window, or for all nodes in a
deprecated=falsebuild.