To anyone interested, the new issue is here:

https://github.com/angular/angular.js/issues/7383

On Wednesday, May 7, 2014 9:55:30 AM UTC-4, Christopher Tang wrote:
>
>
> I'm reviving this thread and I updated the 
> Plunker<http://plnkr.co/edit/pGB1RWFKYMvUW0ImHqyE?p=preview>
> .
>
> The recent fix takes care of the replace: true case, but hasn't fixed the 
> transclude: true or 'element' cases. Is there anything I can do to report 
> this as an issue?
>
> On Wednesday, April 30, 2014 9:20:32 PM UTC-4, Christopher Tang wrote:
>>
>>
>> Plunker demo'ing the fix:
>>
>> http://plnkr.co/edit/pGB1RWFKYMvUW0ImHqyE<http://www.google.com/url?q=http%3A%2F%2Fplnkr.co%2Fedit%2FpGB1RWFKYMvUW0ImHqyE&sa=D&sntz=1&usg=AFQjCNGAWjRBsR_11NRmadT4yefGPD8mcA>
>>
>> On Wednesday, April 30, 2014 8:06:02 PM UTC-4, Christopher Tang wrote:
>>>
>>>
>>> Further scanning the code indicates that the issue was resolved rather 
>>> elegantly, literally yesterday. There is an API change, that appears as of 
>>> yet, undocumented. I suspect it will be public soon enough.
>>>
>>> Here is the issue log discussing the PR into master:
>>>
>>> https://github.com/angular/angular.js/pull/7265
>>>
>>> for:
>>>
>>> commit f0e12ea7fea853192e4eead00b40d6041c5f914a
>>> Author: Caitlin Potter <--redacted-->
>>> Date:   Sat Apr 26 19:35:01 2014 -0400
>>>
>>>     feat($compile): allow SVG and MathML templates via special `type` 
>>> property
>>>
>>>     Previously, templates would always be assumed to be valid HTML 
>>> nodes. In some cases, it is
>>>     desirable to use SVG or MathML or some other language.
>>>
>>>     For the time being, this change is only truly meaningful for SVG 
>>> elements, as MathML has
>>>     very limited browser support. But in the future, who knows?
>>>
>>>     Closes #7265
>>>
>>> I'll post the plunker demonstrating the new feature in a few moments.
>>>
>>> On Wednesday, April 30, 2014 6:17:41 PM UTC-4, Christopher Tang wrote:
>>>>
>>>>
>>>> Thanks for pointing that out.
>>>>
>>>> Here is a plunk <http://plnkr.co/edit/pGB1RWFKYMvUW0ImHqyE?p=preview>that 
>>>> illustrates the issue. 
>>>>
>>>> On Wednesday, April 30, 2014 5:40:58 PM UTC-4, Michel Morelli wrote:
>>>>>
>>>>>
>>>>> Il giorno 30/apr/2014, alle ore 22:28, Christopher Tang <
>>>>> chris....@gmail.com> ha scritto:
>>>>>
>>>>>
>>>>> Apologies for the second post, but I just noticed the guideline about 
>>>>> not posting code, so I removed it. Below is the original message without 
>>>>> code.
>>>>>
>>>>>
>>>>> Best practice is to use (like a start point) 
>>>>> http://jsfiddle.net/IgorMinar/ADukg/  or 
>>>>> http://plnkr.co/edit/tpl:FrTqqTNoY8BEfHs9bB0f to recreate, in code, 
>>>>> the problem that you ask for. 
>>>>>
>>>>> But if you need to include a little piece of code so that we (mailing 
>>>>> list peoples) can understand better your problem, I think that this is 
>>>>> better than 1000 words.
>>>>>
>>>>> M.
>>>>>
>>>>> PS: sorry for bad english.
>>>>>
>>>>> --
>>>>> Davide Morelli
>>>>> ziob...@gmail.com
>>>>>
>>>>>
>>>>>
>>>>>  
>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to