erroneous behavior when setting or submitting form data under PrivilegeManager.enablePrivilege("UniversalXPConnect")

RESOLVED EXPIRED

Status

()

Core
Security: CAPS
RESOLVED EXPIRED
14 years ago
12 years ago

People

(Reporter: Jeremy Lin, Assigned: Mitchell Stoltz (not reading bugmail))

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007

After calling
netscape.security.PrivilegeManager.enablePrivilege("UniversalXPConnect"),
attempting to set form fields exhibits weird behavior, and the form doesn't
appear to submit the data.

Reproducible: Always

Steps to Reproduce:
1. Load the index.html page (see attached files "index.html" and "test.html").
2. Click the "Fill In" button in the top frame a few times.
3. Now try submitting the form.

Actual Results:  
Each click of "Fill In" appends the value, rather than just setting the value of
the field, resulting in multiple copies of "mozilla". The result of submitting
the form appears to be the same as if one had submitted a blank query.

Expected Results:  
The first click should have filled in the form field, and each additional click
should refill it with the same value (effectively, not changing anything). The
form should then have submitted and showed search results for "mozilla".

I lumped both the form field setting and form submission problems into one
report here because I don't feel they're really the central issue. If you save
the Google search page locally and edit it so the form posts to a URL, then the
netscape.security.PrivilegeManager.enablePrivilege("UniversalXPConnect") call
isn't necessary, and everything ends up working as expected. So this really has
something to do with this call and its relations, and I imagine it could affect
a variety of other things too.
(Reporter)

Comment 1

14 years ago
Created attachment 133380 [details]
"index.html"
(Reporter)

Comment 2

14 years ago
Created attachment 133381 [details]
"test.html"
(Reporter)

Comment 3

14 years ago
Sorry, I botched the description a little bit. Each click on "Fill In" actually
submits the form too, but just click the back button and click "Fill In" again.
Also, I forgot to mention that

user_pref("signed.applets.codebase_principal_support", true);

needs to be set in prefs.js, and that in 1.4, I believe the filling-in part
works, but the submitting part also doesn't work.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.