Closed
Bug 70955
Opened 25 years ago
Closed 24 years ago
javascript strict warnings in walletOverlay.js
Categories
(Toolkit :: Form Manager, defect)
Toolkit
Form Manager
Tracking
()
VERIFIED
FIXED
People
(Reporter: bugzilla, Unassigned)
Details
Attachments
(1 file)
|
837 bytes,
patch
|
Details | Diff | Splinter Review |
JavaScript strict warning:
chrome://wallet/content/walletOverlay.js line 269: reference to undefined
property window._content.document.forms
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
Comment 1•25 years ago
|
||
This works for me. Without any more details about how to reproduce this, I have
to close this out as WFM. If you are still seeing this and can give a set of
steps for demonstrating it, then please reopen.
Here is what I did:
1. Added dump statements preceding and following the indicated line in
walletOverlay.js and rebuilt
2. Go to any url. I tried about:blank and also tried the sample1 page from
tasks->privacy->form-manager->demonstration
3. Click the right mouse button to bring up the context menu
At this time I see the output from my two dump statements. But I do not see any
javascript warning message.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 2•25 years ago
|
||
In build 20010316 I'm getting:
Try to capture some form data, and then on the same page rightclick on a input
field.
JavaScript strict warning:
chrome://wallet/content/walletOverlay.js line 171: reference to undefined proper
ty elementsArray[element].type
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 3•25 years ago
|
||
I'm still not able to reproduce this. Can you be more specific and indicate
which form you are working with, which field you fill in and capture, then which
field you right-click on.
Also note that the warning message you are now citing is different from the
warning message you cited when you originally filed this bug report.
Comment 4•25 years ago
|
||
Still not able to reproduce. Since reporter hasn't responded to my request for
additional information, I'm closing this out. If there is still a problem,
please reopen and give specific details.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 6•25 years ago
|
||
Just seen:
JavaScript strict warning:
chrome://wallet/content/walletOverlay.js line 269: reference to undefined
property window._content.document.forms
in todays build. Happened after going to
ftp://ftp.asuscom.de/pub/ASUSCOM/BIOS/Slot_I/INTEL_Chipset/i440BX/P3B-F/
and right-clicking on the page.
The ftp site showhow for some other reason didn't list any files.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Comment 7•25 years ago
|
||
Unable to reproduce. I am, however, seeing the following error messages when I
follow the latest instructions (note the middle message is bug 77022):
JavaScript error:
chrome://communicator/content/nsContextMenu.js line 277:
root.getAttribute is not a function
JavaScript error:
chrome://cookie/content/cookieContextOverlay.xul line 94:
contextMenu has no properties
JavaScript error:
line 0: contextMenu has no properties
Comment 8•25 years ago
|
||
Closing again as works-for-me. Will make additional comments in bug 77022.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 9•25 years ago
|
||
Ok, once again:
Make sure you have user_pref("javascript.options.strict", true); in your
prefs.js
then go to:
1) ftp://ftp.dk.net/
2) open the directory "mirrors"
3) rightclick on the "ftp.cs.hut.fi" directory
js warning is shown in the console.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 10•25 years ago
|
||
this is not a mozilla0.9 stopper. we would like some help fixing this - hence
moving to Future and helpwanted.
Keywords: helpwanted
Target Milestone: mozilla0.9 → Future
Comment 11•25 years ago
|
||
Doesn't make sense to hide this under the rug (marking "future") since it's so
easy to fix and it could be affecting bug 77073 as well.
Problem is occuring because the display for the ftp site is a xul document
instead of an html document and so it doesn't have any forms. Attaching
patch that expicitly tests for that.
Status: REOPENED → ASSIGNED
Target Milestone: Future → mozilla0.9
Comment 12•25 years ago
|
||
Comment 13•25 years ago
|
||
law, please review attached patch. alecf, please super-review. Thanks.
Comment 14•25 years ago
|
||
sr=alecf
Comment 15•25 years ago
|
||
r=law
Comment 16•25 years ago
|
||
Are you still shooting for 0.9 on this? If so please email drivers@mozilla.org
with a status on you progress. If not please retarget against a later Milestone.
Thanks.
Comment 17•25 years ago
|
||
steve, please move this to mozilla0.9.1 unless critical for mozilla0.9. thanks,
Vishy.
Updated•25 years ago
|
Target Milestone: mozilla0.9 → mozilla0.9.1
Comment 18•25 years ago
|
||
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
| Reporter | ||
Updated•24 years ago
|
| Reporter | ||
Comment 20•24 years ago
|
||
Morse... just seen this...:
Warning: assignment to undeclared variable state
Source File: chrome://wallet/content/walletOverlay.js
Line: 253
Comment 21•24 years ago
|
||
This bug report is for undefined property window._content.document.forms and
that has been fixed. This new bug is for variable state and so is a separate
bug report. Please open a new report on it. Also include steps for
reproducing, otherwise there isn't much I can do with it.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 22•24 years ago
|
||
ok... he, he. I have to remember which netscape.com developer who like to have
the bug reopen and which (like you) who like to have a new bug...:)
Status: RESOLVED → VERIFIED
Updated•17 years ago
|
Assignee: morse → nobody
Product: Core → Toolkit
QA Contact: tpreston → form.manager
Target Milestone: mozilla0.9.1 → ---
Version: Trunk → unspecified
You need to log in
before you can comment on or make changes to this bug.
Description
•