Closed
Bug 1481584
Opened 6 years ago
Closed 6 years ago
Image gallery loads only 197 thumbnails out of 249. Tested with new profile, works fine on Chrome not Firefox.
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 256180
People
(Reporter: u621554, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20180621121604 Steps to reproduce: Access a simple static HTML page with thumbnails. 60.1.0esr / 64bit / Windows 7 x64 SP1 Actual results: Image gallery loads only 197 thumbnails out of 249. Expected results: It should load all 249 thumbnails, which works fine on Chrome, but not Firefox, despite having tested it with a CLEAN profile.
To save space I cannot upload the thumbnails, they are small though, same size like windows thumbnails. Since the fallback is alt='' is empty you will stare at a blank black page. If you had the thumbnails only 197 of the 249 would render.
The bug is reproducible on the current Android nightly too. It seems to affect all current channels. If Firefox doesn't want to lose more than it's tiny 11.7 % desktop market share it is a call for action to fix this. Remember, it works on chrome. I cling to Firefox, but trivial issues like these should not happen at all!
I created a tester with demo thumbnails. (see attachments above or below) Trigger the bug with this test.
Comment 4•6 years ago
|
||
This is reproducible using the test file in comment 3. Firefox shows 197 while Chrome shows 249. Test Environment: ----------------- Version 63.0a1 Build ID 20180810100128 Update Channel nightly User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0
Status: UNCONFIRMED → NEW
Component: Untriaged → Layout
Ever confirmed: true
Product: Firefox → Core
Comment 5•6 years ago
|
||
The DOM parser depth is capped at 200 to avoid stack overflows in some systems (particularly win32). Bug 256180 tracks changing that. Chrome just lets the stack overflow and crashes. In any case, you probably want to use <p> instead of <pr> tags, or close your <pr> tags in your page, or something. There's no need to be as rude as comment 2 :)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•