Closed
Bug 211728
Opened 21 years ago
Closed 3 years ago
after showing 200 records from the database, mozilla stops loading the page and breaks the last recor
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gpaolo, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; it-IT; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; it-IT; rv:1.4) Gecko/20030624 I found this problem in a page that showed the content of a database. Maybe it is uncommon to have over 1000 forms in a web page, but Mozilla can't show it correctly. In fact after 199 forms it shows in a wrong way the 200th record. Other browsers display it correctly. Reproducible: Always Steps to Reproduce: 1. Open the submitted link 2. Scroll to the last displayed record 3. Look - there should be 1469 records, but the browser only shows the first 200 Actual Results: The browser stops showing the page after showing 200 records of 1469. The last record is not show correctly Expected Results: The browser should show 1469 records
Comment 1•21 years ago
|
||
.
Assignee: general → form
Component: Browser-General → Layout: Form Controls
QA Contact: general → desale
Comment 3•21 years ago
|
||
Confirming bug, 2003-07-03-22 trunk Linux
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
Comment 4•21 years ago
|
||
Confirmed with Mozilla trunk 2003060404 on WinXP. Source shows complete but page messes up. See attachment for last visible & odd part.
Updated•15 years ago
|
Assignee: layout.form-controls → nobody
QA Contact: desale → layout.form-controls
Hi,
I tested this issue on the latest Nightly version 94.0a1 (2021-10-04) (64-bit) on Windows 10, and I am able to see up to the record number 1469.
I'll be marking this ticket as Resolved - WFM as I understand this is an outdated issue.
Regards,
Virginia
Status: NEW → RESOLVED
Has STR: --- → yes
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•