currently, contrary to the XUL1.0 doc, many (if not all) XUL boolean attributes *only* works when set to "true" and does not work when set to "false".
critical == 'crashes, loss of data, severe memory leak'. Can you also elaborate on what you mean.
Severity: critical → normal
whoops!, my bad, must have accidentally clicked on the wrong dropdown.
Text widgets have this same problem. (Bug 72157)
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.8
huh. I thought I backed out my patch weeks ago. If not (apparently not), reassign this to me, I'll back it out.
Assignee: hyatt → blaker
Status: ASSIGNED → NEW
blake: which patches are you refering to?
I think that it may be why bannerblind (http://bannerblind.mozdev.org)XUL interface works in Netscape 6.2 but not in a recent Mozilla... is it a regression? Or am I writing deprecated XUL code?
*** Bug 120900 has been marked as a duplicate of this bug. ***
Moving non nsbeta1+ XUL 1.0 bugs to mozilla1.2
Target Milestone: mozilla1.0 → mozilla1.2
*** Bug 95949 has been marked as a duplicate of this bug. ***
*** Bug 142030 has been marked as a duplicate of this bug. ***
*** Bug 142028 has been marked as a duplicate of this bug. ***
This is something that I would definitely want to see get some traction, since it has a patch. Also, it seems to break a lot of embeddors and XUL hobbyists. :-) Blake, would you take a look at your patch, and update it to the trunk if it is still relevant?
what is the status on this, do we still care about this? I could write patches if someone wants this fixed.
Assignee: bross2 → nobody
QA Contact: jrgmorrison → xptoolkit.xul
Sorry for the dup, but isn't it time to solve this???
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.xul → xptoolkit.widgets
C'mon guys, 10 years old bug and it still not fixed?
You need to log in before you can comment on or make changes to this bug.