Closed
Bug 486870
Opened 15 years ago
Closed 15 years ago
Camino unable to render and display page elements unlike all other browsers
Categories
(Camino Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 334321
People
(Reporter: yxf4, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.21) Gecko/20090327 Camino/1.6.7 (like Firefox/2.0.0.21pre) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.21) Gecko/20090327 Camino/1.6.7 (like Firefox/2.0.0.21pre) going to the given URL in camino, the page will initially render, then all elements will vanish. This makes using the site impossible as the content vanishes as soon as you try to scroll down. parts will appear only when you mouse over them. The boarder of the site is fine. The site works perfectly, and without stuttering, in all other browsers (Safari, Firefox, etc.) Reproducible: Always Steps to Reproduce: 1. Go to site 2. See bad behavior 3. Use another browser and enjoy browsing excellence Actual Results: central page elements stutter and vanish Expected Results: page elements should render and remain correctly and not stutter It is my impression that Camino uses the same rendering core as Firefox, and yet Camino often can not display sites correctly, where as Firefox has no issue. I prefer Camino's interface, but it's inability to use a lot of sites and bizarre CPU throttling makes it a poor choice of browser
I see the same behavior in Camino 1.6.7 as in Firefox 2.0.0.20, namely bug 334321. That Gecko bug is fixed in Camino 2.0b2 and Firefox 3.0.x on Intel; when I visit that page with those versions, I do not see any problem with content disappearing.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Component: Page Layout → Plug-ins
QA Contact: page.layout → plugins
Resolution: --- → DUPLICATE
Updated•15 years ago
|
Status: RESOLVED → VERIFIED
Comment 2•15 years ago
|
||
1.6.8 only displays part of site see <http://www.westorange.org> missing bacground
You need to log in
before you can comment on or make changes to this bug.
Description
•