input.blur() throws "Permission denied to set property XULElement.selectedIndex"

NEW
Unassigned

Status

()

10 years ago
10 years ago

People

(Reporter: dhtmlkitchen, Unassigned)

Tracking

({testcase})

3.5 Branch
x86
Windows XP
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
Created attachment 355699 [details]
testcase showing problem

When calling blur() on an input, the error is sometimes thrown:
"Permission denied to set property XULElement.selectedIndex"
Steps to repro:
1. load attachment 1 [details] [diff] [review]
2. focus the input manually
3. submit the form (via enter)
4. focus the input manually
5. delete the last "0"
6. reload the page

Actual Results:
Two errors:
Permission denied to get property XULElement.popupOpen
[Break on this error] zip.blur();
blur-tes...zip=90000 (line 18)
Permission denied to set property XULElement.selectedIndex
[Break on this error] zip.blur();

Expected Result: 
Instead, no error should be thrown. XULElement errors should not occur with normal user interaction. If they do, they should be hidden away from the browser and should not be propagated to the browser front end.

This may be related to autocomplete. 

See also: Bug 470968,  Bug 236791
This may be the cause of all those errors I see when using gmail... unless, is this really only 3.1 branch?

Comment 2

10 years ago
This is a longstanding bug in Firefox and it got worse with the awesomebar. When the awesomebar is active blurring a textedit can also trigger the errors. (without reloading the page).
The fact that the awesome bar can also help trigger the can be seem
by using Garett Smith's testcase (Attachment 1 [details] [diff])
and following these alternative steps:

1. load attachment 1 [details] [diff] [review]
2. focus the input manually
3. click on the url
4. activate the 'awesomebar' (arrow down)
5. reload the page


There are many mentions of setting autocomplete="off" on the <input> as workaround. This also fixes the problem in the cms/framework we create and use at our company.

As far as I can remember we also had the errors appear in Firefox 2.
Here's an example of a thread started in 2005 which mention the bug and workaround:
http://codingforums.com/showthread.php?t=61320
In that thread someone mentions finding a reference to it in Bugzilla, but I havn't had any luck finding it yet.

Comment 3

10 years ago
Found the reference they mentioned. Bug 236791 seems to be the same issue.
It was reported in 2004 for Firefox 0.8 and was fixed for Gecko 1.8.1 (Firefox 2), although the issue never seemed to have gone away. (maybe focus() was fixed, but not blur() ??)

Comment 4

10 years ago
Which build are you using?

The version of this bug is set to 3.1 branch and "Permission denied to set property XULElement.selectedIndex" is in the summary but they are inconsistent.
The message in 3.1 branch is "Permission denied for <%S> to set property %S.%S."
You need to log in before you can comment on or make changes to this bug.