This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
3.2.3.4 The translate attribute http://www.w3.org/TR/html5/dom.html#the-translate-attribute The list of translatable attributes suggests that any values of attributes not on the list should not be translated, but this is not explicitly stated. I assume that it is the case that values of attributes not listed are non-translatable whether or not the element on which they sit is set to translate. I'm also not entirely clear what happens when the value of an attribute in the list appears on an element that has translate set to no.
Commit pushed to master at https://github.com/w3c/html https://github.com/w3c/html/commit/572aa7b55bcf60eb7f1e8642f1203229ad20e70c [Bug 23208]: Be more explicit about translate attribute behavior. Fixes https://www.w3.org/Bugs/Public/show_bug.cgi?id=23208
It seems that the most intuitive behavior would be to only translate translatable attributes when their element is in the translate-enabled state, and in all other cases not to translate an element's attribute values. As I read it, this is the behavior currently described in the spec, but I'd be happy to take a stab at making this more explicit: https://github.com/w3c/html/commit/572aa7b55bcf60eb7f1e8642f1203229ad20e70c Is there usage data or use cases suggesting otherwise? I'm having a hard time imagining why one might want to translate the translatable attributes but not the text node children of an element. If the clarification looks okay, I'll merge it into the HTML5 CR spec.
(In reply to Erika Doyle Navara from comment #2) > It seems that the most intuitive behavior would be to only translate > translatable attributes when their element is in the translate-enabled > state, and in all other cases not to translate an element's attribute > values. > > As I read it, this is the behavior currently described in the spec, but I'd > be happy to take a stab at making this more explicit: > > https://github.com/w3c/html/commit/572aa7b55bcf60eb7f1e8642f1203229ad20e70c > > Is there usage data or use cases suggesting otherwise? I'm having a hard > time imagining why one might want to translate the translatable attributes > but not the text node children of an element. > > If the clarification looks okay, I'll merge it into the HTML5 CR spec. The clarification looks good to me. - Felix
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: Making translation behaviors of attributes under translate-enabled and no-translate states of an element a little more explicit. Rationale: Clarifies intended behavior of the translate attribute for web authors and implementers of localization tools (no normative changes).
Commit pushed to master at https://github.com/w3c/html https://github.com/w3c/html/commit/32c3e93f765dde4b0873c519cd4728305bada5f0 Adding W3C fork markers for HTML5 CR bug 23208.
Commits pushed to CR at https://github.com/w3c/html https://github.com/w3c/html/commit/8c743ed23b2006f9bd738735b703b21a54fb4a0b [Bug 23208]: Be more explicit about translate attribute behavior. Fixes https://www.w3.org/Bugs/Public/show_bug.cgi?id=23208 https://github.com/w3c/html/commit/af58f280cb43e860043a81ce436dda9fa9d03a95 Adding W3C fork markers for HTML5 CR bug 23208. Conflicts: source
Commits pushed to CR at https://github.com/w3c/html https://github.com/w3c/html/commit/572aa7b55bcf60eb7f1e8642f1203229ad20e70c [Bug 23208]: Be more explicit about translate attribute behavior. Fixes https://www.w3.org/Bugs/Public/show_bug.cgi?id=23208 https://github.com/w3c/html/commit/32c3e93f765dde4b0873c519cd4728305bada5f0 Adding W3C fork markers for HTML5 CR bug 23208.