196707 - doubleclick on link crashes phoenix when page is loaded via --chrome

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[Marc Schmitt]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.1; Linux 2.4.19-4GB; X11; i686; de, de_DE@euro)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5

On some special pages, phoenix crashes when doubleclicking on any link in the 
document, when it's loaded via the --chrome option. 
 
This is not working with all documents, but some special ones within our 
intranet-webserver. Those documents heavily rely on frames an javascript, and have 
onmouseover handlers on most links. 

Reproducible: Always

Steps to Reproduce:
[ this only seems to work with some, special pages, not with all. But within these pages, 
it works always, on linux as well as on windows ] 
1. ./phoenix --chrome http://ourserver/document.html 
2. <doubleclick on some link in the document > 
 
Actual Results:  
Phoenix crashes.  
It feels like (on windows) phoenix crashes instantly, during the 2nd click of the 
doubleclick. ondblclick doesn't get processed too. But when I click slowly, that no 
dblclick gets generated, nothing happens. 

Expected Results:  
Open the page normaly.

Comment 1

[David Tenser [:djst]]

I can confirm that there are some interesting issues when using the --chrome
switch. When opening Phoenix Help with that switch
(http://texturizer.net/phoenix/), the window title is replaced with either
"null" or "LockedMenu", which is the names of the stylesheet currently in use. 

So there _are_ bugs with the --chrome switch, but I cannot make it crash. Cc'ing
a few good QA's.

Comment 2

[David P James]

I'm not seeing the specific problem identified in the original bug report (I
can't crash it either) but I am seeing what David mentionned, and other assorted
weirdness. However I am not sure what is meant by "double clicking on a link" as
the concept of doing that doesn't make any sense to me.

Uploading a test case or specifying a "special" page would help as well.

More generally I'm not even sure what the purpose of the --chrome switch is so
I'm not sure what it is I should be seeing, except that what I am seeing is
probably not correct.

Comment 3

[Marc Schmitt]

Attachment: crashes pheonix on startup when uses with --chrome http://localhost:8000/index.html (linux)

Comment 4

[Marc Schmitt]

I've added a sample from our internal webserver ... but it is interesting. When started 
from our server, it crashes phoenix when doubleclicking on a link.  
But when started separetly, phonix grabs all available memory and crashes on startup 
... hmm. 
 
Output : 
 
test@titan98:~/local/phoenix> ./phoenix --chrome http://localhost:8000 
Gdk-ERROR **: BadAlloc (insufficient resources for operation) 
  serial 1485 error_code 11 request_code 53 minor_code 0 
Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter) 
  serial 1486 error_code 9 request_code 55 minor_code 0 
 
 

Comment 5

[noririty]

Reporter:
Can you reproduce with recent "Mozilla"?

BTW this -chrome usage seems improper. Suggest invalid.

Comment 6

[Marc Schmitt]

Sorry, I'm not on this project anymore. We've swiched to IE.  
 
But the main reason for this were not the chrome-errors, but phoenix(mozilllas) very long 
startup time when loaded from cd-rom. 
 

Comment 7

[noririty]

-> invalid