- From: <jerome.giraud@orange.com>
- Date: Tue, 27 Mar 2012 13:42:52 +0000
Hi, We had already planned on finding a replacement for our HTML Element extensions and I think the current discussions will force us to speed things up, which is a good thing :) This was a "legacy" feature that we decided we should get rid of a long time ago for these obvious conflicts reasons, though we had never imagined the "translate" would be used on HTMLElements in an i18n context (so +1 for Edward O'Connors comment if I may) I already warned the persons in charge of the Orange portal and they will replace the HTMLElement.translate calls. We will warn our users and prepare the necessary changes for our next release. J?r?me Wink Toolkit >We >WebKit recently implemented >http://www.whatwg.org/specs/web-apps/current-work/#attr-translate, but >that caused us to break orange.fr on mobile: > >https://bugs.webkit.org/show_bug.cgi?id=82246 > >The problem is that >http://www.winktoolkit.org/documentation/symbols/HTMLElement.html#translate >has a the following code: > >if (wink.isUndefined(HTMLElement.prototype.translate)) > HTMLElement.prototype.translate = HTMLElement.prototype.winkTranslate; > >The web site expects HTMLElement.prototype.translate to be Wink's >translate function rather than the HTML translate attribute. > >Would it make sense to change the name of the translate attribute to >avoid this conflict? Should we try to evangalize the Wink Toolkit to >change their code and everyone who uses Wink to update to the fixed >version? > >Adam
Received on Tuesday, 27 March 2012 06:42:52 UTC