Closed
Bug 48264
Opened 25 years ago
Closed 25 years ago
Mispelled error message: 'qulaified' on any scrollbar click
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: fosterd, Assigned: jst)
Details
Attachments
(1 file)
Using linux CVS from 080913, I get the following error message several (3) times
whenever I click on a (gfx) scrollbar:
Possible DOM Error: .name, .nodeName or .tagName requested on a namespace
element/attribute with the qulaified name 'xul:spring', is this OK?
'qulaified' should probably read 'qualified'. Ideally, this error should go away.
Comment 1•25 years ago
|
||
I have a two-line patch to fix the output of these messages (both for
when using the scrollbars (actually when starting a drag), and for middle
mouse on the scrollbar). I'll attach it in a moment. They both occur when
the event starts in XBL content that is 'xul:' namespaced (i.e., the xul:thumb,
xul:slider, and xul:spring of scrollbar)
(I think the spelling error can stay; that warning is going away completely
someday I believe.)
Comment 2•25 years ago
|
||
Comment 3•25 years ago
|
||
jst -- the patch clears up the warnings (and does the right thing). I ran this
on mac/linux/win32 (the last two with current builds) and checked scrolling and
D&D, plus pre-checkin tests. Since I have no CVS account, would you check this
in (if review of the two-line change looks good :-]).
Comment 5•25 years ago
|
||
it's been a bit, what's the status for this? jst@netscape.com, can you check
this in? Or has this been checked already?
Comment 6•25 years ago
|
||
jst checked this in last night. Marking FIXED. Thanks jst.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 7•25 years ago
|
||
Yup, this was fixed, the error message is all gone now and I also checked in the
attached patch some time back. Thanks for the patch and sorry for forgetting to
update this bug.
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•