184830 - These pages rendered ok until I installed 0.5: gentoo.org, arstechnica.com

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Rob Torop]

User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5

In http://www.arstechnica.com, the page comes up with a correctly rendered top
frame, but all other content is missing.

In http://www.gentoo.org, part of the page (lower right) renders incorrectly. I
believe it's implemented as a table with this part being a single <td>

Reproducible: Always

Steps to Reproduce:
1. Load http://www.arstechnica.com
2. Load http://www.gentoo.org


Actual Results:  
See Details.

Expected Results:  
Correctly rendered the pages

It's hard for me to say how major a bug this is.  I use these sites often and so
it's stops me from using phoenix 0.5 as my default.  I will probably stick with
0.4 to be honest, i.e. I'm not switching to ie :-)

Appended is  my user.js.  But I also tried it with user.js renamed to
user.js.saved and got the same result.  I'm using the phoenity theme.

// Stop reusing active windows:
user_pref("advanced.system.supportDDEExec", false);

// TypeAhead Find Configuration:
// Set this pref to false to disable TypeAhead Find:
// user_pref("accessibility.typeaheadfind", true);
// Set this pref to false if you want TypeAhead Find to search normal text too:
user_pref("accessibility.typeaheadfind.linksonly", false);
// Set this pref to true if you require that the link starts with the entered text:
//user_pref("accessibility.typeaheadfind.startlinksonly", false);
// This is the time in milliseconds for the TypeAhead Find to stop watching for
keystrokes:
//user_pref("accessibility.typeaheadfind.timeout", 3000);


// Change to normal Google search:
user_pref("keyword.URL", "http://google.com/search?btnG=Google+Search&q=");

// Put an end to <blink> tags!
user_pref("browser.blink_allowed", false);

// This one makes a huge difference. Last value in milliseconds (default is 1200)
user_pref("nglayout.initialpaint.delay", 0);

// Enable pipelining:
//user_pref("network.http.pipelining", true);
//user_pref("network.http.proxy.pipelining", true);
//user_pref("network.http.pipelining.maxrequests", 100);

// Specify the amount of memory cache in kilobytes:
user_pref("browser.cache.memory.capacity", 8192);

Comment 1

[Simon Paquet [:sipaq]]

WFM using Mozilla/5.0 (Windows NT 5.0; en-US; rv:1.3a) Gecko/20021209 Phoenix/0.5

Try a newer build and report back. Have you done a clean install as suggested in
the release notes?

Comment 2

[Rob Torop]

I have three builds of Phoenix installed: 0.4, 0.5, and a nightly build (from 11
Dec).  In the first two, I renamed the defaults/profile directory to
profile.saved.  I then ran the nightly build and had the same rendering problem.
 Does it work ok for you guys?

Comment 3

[jon moses]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5

WFM.

Comment 4

[Sébastien Delahaye]

WFM using Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a)
Gecko/20021222 Phoenix/0.5

Rob, could you please try with a *new* (ie. untouched and not modified) profile?

Comment 5

[flii (cj)]

wfm as well.

Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3a) Gecko/20021227 Phoenix/0.5

Comment 6

[Ryuichi KUBUKI]

WFM on 20030116 nightly on WinXP

Comment 7

[Asa Dotzler [:asa]]

both pages render as expected in a build from this morning on windows and linux.