After some tweaking around in the angular code because XULrunner returns 0 as
status for successful xhr request made to local resources (on disk) I am
running into yet another obstacle.
Any link that's manipulated by angular stops working:
<a href='#/students/JON'>Wors</a>
<a href='#/students/{{"JON"}}'>doesnt work</a>
Yet links that are dynamically added work fine too
var a=document.createElement("a");
a.href="#/students/JON";
a.innerHTML="JS added works fine";
document.body.appendChild(a);
The html file is in a XUL browser element and all the scripts and templates are
located in chrome://myapp/content/. After having angular accept 0 as a
successful return status, loading the templates and binding the data XUL
descides it's time to mess with the links.
Working links have a href of: chrome://myapp/content/index.html#/students/JON
Non working: unsafe:chrome://myapp/content/index.html#/students/JON
This only happens to elements that angular binds data to. Not sure why this
feature of XUL would do this because all links point to resources located in
chrome://myapp/content/
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
