"observes" attribute in a textbox

[anton1981]

Hi,
when I add an "observes" attribute to a textbox it becomes read-only, meaning I can't edit it's input.
The textbox resides in a preference window.

Code: Select all

<textbox id="antonpod-et-textbox" minwidth="300" change="antonpod.et.onChange(event);" observes="antonpod-et-emptybr"/>


Why is this happening and what's the way around this, if any?
Tnx.

[anton1981]

This is the broadcaster element:

Code: Select all

<broadcasterset>
      <broadcaster id="antonpod-et-enbr" disabled="false"/>
      <broadcaster id="antonpod-et-emptybr" disabled="false"/>
</broadcasterset>


[max1million]

Try the oncommand, onclick or some such on the antonpod-et-emptybr to make the switch, may also need onload or onsynfrompreference to check antonpod-et-emptybr and set antonpod-et-textbox.

[anton1981]

Try the oncommand, onclick or some such on the antonpod-et-emptybr to make the switch, may also need onload or onsynfrompreference to check antonpod-et-emptybr and set antonpod-et-textbox.

I'm not sure I follow your solution...
I use the broadcaster to automatically disable/enable multiple elements in a preference window, instead of changing the "disabled" attribute of each of them separately.
Somehow this makes the textbox which listens to the broadcaster to be read-only, while I need it to be able to get input. May it be that the textbox shares some default "readonly" attribute of the broadcaster?

[max1million]

Change it separately, for that one.

May be with using observes on textbox the normal idea would be to observe a value rather then user input, dunno haven't done. Of course it should go without saying that if the element being broadcasted is disabled, since that is what is being broadcast, then so would be the textbox, and therefore readonly, since input would be disabled.

[anton1981]

Change it separately, for that one.

This is always an option, yes.

Of course it should go without saying that if the element being broadcasted is disabled, since that is what is being broadcast, then so would be the textbox, and therefore readonly, since input would be disabled.

Sure, in my case when the textbox is enabled I can't edit/copy it's current value.

[max1million]

OK just fiddled with it and it seems that as long as there is an attribute for disabled the property disabled is true.

[anton1981]

OK just fiddled with it and it seems that as long as there is an attribute for disabled the property disabled is true.

Disabled elements are grayed out, but here the textbox appears enabled.
Should I just report a bug and see what people are saying?

[fcp]

when I add an "observes" attribute to a textbox it becomes read-only, meaning I can't edit it's input.

Are you trying to observe the “value” attribute? If so, you may have run into bug 183776. Actually, setting the value attribute (instead of the value property) of a textbox seems currently problematic no matter whether you set it via a broadcaster or directly; see bugs 184732 and 277892.

[anton1981]

Are you trying to observe the “value” attribute?

No, just the the "disabled" attribute.

[fcp]

Are you trying to observe the “value” attribute?

No, just the the "disabled" attribute.

Then see bug 174492, which is Wontfix. I am afraid that the only way to avoid the problem is giving up using the broadcaster.

[anton1981]

Then see bug 174492, which is Wontfix. I am afraid that the only way to avoid the problem is giving up using the broadcaster.

fcp, thanks for the info.