User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030515 Mozilla Firebird/0.6 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030515 Mozilla Firebird/0.6 When entering into the itme edit are (after loging into http://demo.icdevgroup.org/i/demo1/admin with demo demo) choosing items and then slecting a product to edit causes on Mac, Power Mac, PC ALL (MS, LINUX) to crash. This is a problem with all browsers using mozilla build from 1.3 on up. For some reason using Phoenix 0.5 (released version on site) does not dump or crash on LINUX, have not tested on any other platform. Phoenix 0.6, and All mozilla builds from 1.3 are fully reproducable. Reproducible: Always Steps to Reproduce: 1. Login to site (demo demo) 2. Choose Items 3. Select a product to edit 4. Watch Actual Results: Browser crashes. Expected Results: Not crashed Mozilla just disappears, nothing more
WFM with my Linux trunk build from yesterday.
confirming using Firebird 20030529 on Win2k: TB20617263X.
Assignee: general → other
Status: UNCONFIRMED → NEW
Component: Browser-General → Layout
Ever confirmed: true
QA Contact: general → ian
Setting Hardware=All per comment 0.
Hardware: PC → All
Whiteboard: TB20617263X → Look up TB20617263X
steps to reproduce: 3.5. click "Edit checked"
Created attachment 124650 [details] testcase load the testcase (nothing) reload the testcase => crash <body onload="document.getElementById('mvpanpanel0').style.display='none';"> <input style="position:absolute" id="mvpanpanel0" type="file"> </body>
Created attachment 124652 [details] stacktrace from testcase (quite a bit shorter) the stack is completely different, suggesting a different bug, but I removed the <input type=file> tags from the original URL and it loaded fine
Attachment #124648 - Attachment is obsolete: true
==> form controls this regressed between linux trunk 2002121908 and 2002122008, placing blame on bug 152844
Assignee: other → jkeiser
Component: Layout → Layout: Form Controls
Keywords: regression, testcase
This crash has the same stack as bug 203041 and is caused by the same line as mentioned in bug 203041 comment 6. *** This bug has been marked as a duplicate of 203041 ***
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.