You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. When a string belonging to a component* being temporarily closed for contributions is cause of inconsistency with other occurrences while a translation of a string belonging to a non-locked component is made, the invocation of Apply selected translation to all propagated strings is intended to not apply to those strings whose components are in locked state and therefore does behave so.
Illustration of locked component:
Nevertheless unlike that view where the component in locked state can be identified by the presence of an icon representing a lock, the lack of association of that very icon with a component being in locked state in the interface shown in the Screenshots section, cannot lead to conclude of that state and shall legitimately lead to conclude that the expected failures that occur when invoking that propagation are an indication of an issue, which it is not.
Describe the solution you'd like
Associating the presence of a such icon with each component being in locked state also in the interface shown in the Screenshots section.
Describe alternatives you've considered
No response
Screenshots
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the problem
Hello. When a string belonging to a component* being temporarily closed for contributions is cause of inconsistency with other occurrences while a translation of a string belonging to a non-locked component is made, the invocation of Apply selected translation to all propagated strings is intended to not apply to those strings whose components are in locked state and therefore does behave so.
Nevertheless unlike that view where the component in locked state can be identified by the presence of an icon representing a lock, the lack of association of that very icon with a component being in locked state in the interface shown in the Screenshots section, cannot lead to conclude of that state and shall legitimately lead to conclude that the expected failures that occur when invoking that propagation are an indication of an issue, which it is not.
Describe the solution you'd like
Associating the presence of a such icon with each component being in locked state also in the interface shown in the Screenshots section.
Describe alternatives you've considered
No response
Screenshots
Additional context
No response
The text was updated successfully, but these errors were encountered: