Closed Bug 273999 Opened 21 years ago Closed 20 years ago

Error parse ListBox from string

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: rusanov, Unassigned)

Details

Attachments

(4 files)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; ru-RU; rv:1.7.5) Gecko/20041108 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; ru-RU; rv:1.7.5) Gecko/20041108 Firefox/1.0 I try parse string with listbox element var string="<listbox flex='1' xmlns='http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul'>"; for(i=0; i < len; i++) { string += '<listitem>' + '<vbox>' + '<hbox>' + '<label class="header" value="device:"/>' + '<description>Elecsys 2010</description>' + '</hbox>' + '<hbox>' + '<label class="header" value="sp:"/>' + '<description>serum</description>' + '</hbox>' + '<button label="mozilla"/>'+ '</vbox>' + '</listitem>' } string+="</listbox>"; I add var node = parser.parseFromString(string, "text/xml") list.appendChild(node.documentElement); if I use my sample with protocol chrome (chrome://) istbox wrong behaviour, in javascript console error Error: uncaught exception: Permission denied to get property MouseEvent.ctrlKey Error: uncaught exception: Permission denied to get property MouseEvent.button if I use my sample with protocol file file:/// listbox behaviour currect Reproducible: Always Steps to Reproduce: 1. 2. 3.
Attached file run this example
Attached file run this example
Summary: Error parse ListBox from string → Error parse ListBox from string
So what are the steps to reproduce this? Loading the attachment doesn't throw any errors in the JS console, and the attachment doesn't say what the expected behavior is....
You must run this attachment using chrome protocol, for example chrome://samplechromeapp/content/Test.xul when I run this attachment in chrome, listbox show incorrect listitems if I run this attachment in file profotol (file:///C:/prj/dcxulapp/laboratory/content/laboratory/Test/builddom/Test.xul), listbox show correct listitems I test this attachment in Mozilla 1.8a5 Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122
When try test in build Mozilla 1.8a6 Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20050111 then i get the same result.
Why does it need to run as chrome? Would file:/// with UniversalXPConnect privileges also work? If so, can you write up a testcase to that effect? Installing chrome changes is not something that I'm willing to undertake lightly....
Attached file xpi
this xpi
I try run sample in file:/// with UniversalXPConnect , listbox show correct listitems
run this link chrome://laboratory/content/Test/builddom/Test.xul
run this example with "file:///" and with "chrome://" and you will see difference
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
Closed: 20 years ago
Resolution: --- → EXPIRED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: