Closed
Bug 822104
Opened 12 years ago
Closed 11 years ago
certain pages don't load completely
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: hlein, Assigned: khuey)
References
()
Details
(Keywords: regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 Build ID: 20121205060959 Steps to reproduce: Browse to http://digi.ceskearchivy.cz/DA?lang=de&menu=3&id=3988 Actual results: page loaded incompletely, some information and parts of navigation bar missing Expected results: should load completely. Sometimes, after a few minutes the rest of the page comes up. At the left side there should be 3 little boxes with thumbnails of previous and next image, at the bottom should be a navigation bar (forward, backward, first, last image, dropdown box) This does not happen with Internet explorer, it also happens with Firefox 17.0.x. It did not happen with older versions of firefox (around 14.x or 15.x)
Reporter | ||
Updated•12 years ago
|
Reporter | ||
Comment 1•12 years ago
|
||
Reporter | ||
Comment 2•12 years ago
|
||
Comment 3•12 years ago
|
||
Confirmed using Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20121216 Firefox/20.0 ID:20121216030851. * Changing Viewport Size makes the Navigation UI/Preview Thumbnails appear. * reloading the Site does the same To get the Issue back in the same Browser Session I had to clear Cache and hit CRTL+F5 several Times - if at all.
Keywords: regression,
regressionwindow-wanted
Reporter | ||
Comment 4•12 years ago
|
||
> To get the Issue back in the same Browser Session I had to clear Cache and hit CRTL+F5 several Times - if at all.
Alternatively, you may choose another image. Very probably, the error will occur again.
Comment 5•12 years ago
|
||
(In reply to Helmut Leininger from comment #4) > Alternatively, you may choose another image. Very probably, the error will > occur again. As it seems it's not that easy over here for me. Also clearing the Cache/CTRL+F5'ing doesn't make the Issue happen reliably; thus I'm not able to do a proper Regression Range Search :-/. If you want to, you can help using https://github.com/mozilla/mozregression/ and https://wiki.mozilla.org/RapidRelease/Calendar; i.e. start with a Branch Version with has the Issue when it hit Central.
Comment 6•12 years ago
|
||
Regressio window(m-c) Good: http://hg.mozilla.org/mozilla-central/rev/b1775e08bb16 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0 ID:20121012032003 Bad: http://hg.mozilla.org/mozilla-central/rev/83e8792a147a Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0 ID:20121012040504 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b1775e08bb16&tochange=83e8792a147a Regressio window(m-i) Good: http://hg.mozilla.org/integration/mozilla-inbound/rev/a27a41c7d7e3 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0 ID:20121011091302 Bad: http://hg.mozilla.org/integration/mozilla-inbound/rev/c58bfc3f6b48 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0 ID:20121011100002 Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=a27a41c7d7e3&tochange=c58bfc3f6b48 Suspected: Bug 791571
Blocks: 791571
Status: UNCONFIRMED → NEW
status-firefox17:
--- → affected
status-firefox-esr17:
--- → affected
tracking-firefox18:
--- → ?
tracking-firefox19:
--- → ?
tracking-firefox20:
--- → ?
tracking-firefox-esr17:
--- → ?
Component: Untriaged → DOM: Core & HTML
Ever confirmed: true
Keywords: regressionwindow-wanted
Product: Firefox → Core
Version: 18 Branch → 17 Branch
Reporter | ||
Comment 7•12 years ago
|
||
using moznightly I have seen: good: 2012-10-12 bad: 2012-10-13
Comment 8•12 years ago
|
||
Given the workarounds in comment 3, no need to track for release. We would accept a low risk uplift to FF19 if found, however.
Reporter | ||
Comment 9•12 years ago
|
||
@comment 3 even after this bypass, it occurs again in the same session with other images of the same site.
Comment 10•12 years ago
|
||
(In reply to Alex Keybl [:akeybl] from comment #8) > Given the workarounds in comment 3, no need to track for release. We would > accept a low risk uplift to FF19 if found, however. I can not reproduce the workaround. I always get corruption even if reload, clear cash reroad... So i set flags again.
Comment 11•12 years ago
|
||
I'm the webmaster of digi.ceskearchivy.cz From local site everything works OK even in FF 18b4, but from internet there is above described problem.
Comment 12•12 years ago
|
||
Can we verify that bug 791571 is the regressing issue by testing that 17.0b1 is unaffected and 17.0b2 is affected? We can assign to Kyle to be resolved in the FF19 timeframe once confirmed.
status-firefox18:
--- → wontfix
Comment 13•12 years ago
|
||
Yes, version 17.0b1 works well, 17.0b2 doesn't work. So 17.0b1 is unaffected and 17.0b2 is affected.
Comment 14•12 years ago
|
||
Kyle, can you please help with some investigation here ? Thank you !
Comment 15•11 years ago
|
||
this hasn't been a critical issue post-release, so no need to track for future releases.
Assignee | ||
Comment 16•11 years ago
|
||
I don't remember which bug, but we fixed this some time in the Firefox 21 cycle. It WFM on Nightly and Aurora.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•