Closed
Bug 118683
Opened 24 years ago
Closed 2 years ago
XUL boolean attributes only work when set to "true"
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
RESOLVED
INVALID
mozilla1.2alpha
People
(Reporter: basic, Unassigned)
References
Details
(Whiteboard: [xul1.0-widgets-all])
Attachments
(1 file)
|
61.91 KB,
patch
|
Details | Diff | Splinter Review |
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".
|
||
Comment 1•24 years ago
|
||
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.
|
|
||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [xul1.0-widgets-all]
Target Milestone: --- → mozilla0.9.8
|
|
||
Comment 4•24 years ago
|
||
huh. I thought I backed out my patch weeks ago. If not (apparently not),
reassign this to me, I'll back it out.
|
|
||
Updated•24 years ago
|
Target Milestone: mozilla0.9.8 → mozilla0.9.9
|
|
||
Comment 7•24 years ago
|
||
|
|
||
Comment 8•24 years ago
|
||
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?
|
|
||
Comment 9•24 years ago
|
||
*** Bug 120900 has been marked as a duplicate of this bug. ***
|
|
||
Updated•24 years ago
|
Target Milestone: mozilla0.9.9 → mozilla1.0
|
|
||
Comment 10•24 years ago
|
||
Nav Triage: marking nsbeta1-, not needed for Mach V
|
||
Updated•24 years ago
|
Keywords: mozilla1.0+
|
|
||
Comment 11•24 years ago
|
||
Moving non nsbeta1+ XUL 1.0 bugs to mozilla1.2
Target Milestone: mozilla1.0 → mozilla1.2
|
|
||
Updated•24 years ago
|
Keywords: mozilla1.0+ → mozilla1.0-
|
|
||
Comment 12•24 years ago
|
||
*** Bug 95949 has been marked as a duplicate of this bug. ***
|
|
||
Comment 13•24 years ago
|
||
*** Bug 142030 has been marked as a duplicate of this bug. ***
|
|
||
Comment 14•24 years ago
|
||
*** Bug 142028 has been marked as a duplicate of this bug. ***
|
|
||
Comment 15•24 years ago
|
||
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?
|
|
Reporter | |
Comment 17•23 years ago
|
||
what is the status on this, do we still care about this? I could write patches
if someone wants this fixed.
|
||
Updated•19 years ago
|
Assignee: bross2 → nobody
QA Contact: jrgmorrison → xptoolkit.xul
| Comment hidden (advocacy) |
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.xul → xptoolkit.widgets
|
||
Comment 23•14 years ago
|
||
| advocac | ||
C'mon guys, 10 years old bug and it still not fixed?
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Comment 24•3 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 8 duplicates.
:enndeakin, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(enndeakin)
|
||
Comment 25•3 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Flags: needinfo?(enndeakin)
|
||
Comment 26•2 years ago
|
||
No longer relevant with XUL removal
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•