|
Hello,
i have a problem with the broadcaster in a special case.
If i delete an element which is observing the broadcaster and then i create a new one which is observing too,
then only the old element listens to the broadcaster and the new one not.
I modified your demo to make an example:
<script type="text/javascript">
function setState(event) {
event.target.setAttribute('disabled', event.attrValue=='true'?'false':'true');
event.preventDefault();
}
</script>
<div>
<label>Enable
<input id="checkbox" type="checkbox" checked="checked">
<e:handler event="change" type="text/javascript">
var oBroadcaster = bb.document.getElementById('broadcaster');
oBroadcaster.setAttribute('disabled', this.getProperty('checked')?'false':'true');
</e:handler>
</input>
</label>
<b:broadcaster id="broadcaster" disabled="false" />
<b:button e:observes="broadcaster" margin="0 0 20px 0">Create New
<e:handler event="click" type="text/javascript">
<![CDATA[
var oParent = this.getProperty('parentNode');
var sElementNamespaces = "xmlns:b='http://www.backbase.com/2006/btl' xmlns:e='http://www.backbase.com/2006/xel'";
var sElementAttributes = "e:observes='broadcaster'";
bb.command.create('<b:button ' + sElementNamespaces + ' ' + sElementAttributes + ' />',oParent,'appendChild');
]]>
</e:handler>
</b:button>
<b:button e:observes="broadcaster" margin="0 0 20px 0">Delete this
<e:handler event="click" type="text/javascript">
<![CDATA[
bb.destruct(this);
]]>
</e:handler>
</b:button>
</div>
Follow this steps:
- click enable -> buttons disable
- press create new, click enable -> the new button disable too
- press delete this, press create new, click enable -> only the old buttons disable !!
plz help me i need this feature,
thanks
Béla Varga
Hi Bela, Thank you for
7 July, 2009 - 14:11 — yudiHi Bela,
Thank you for reporting the issue.The issue is broadcaster does not propagate automatically to new
created observer element after one of observer element is destroyed.I can reproduce the issue from your provided test code and I have administer this into our issue tracking system. Unfortunately, there is still no workaround yet at this moment.
~Yudi