Closed Bug 273005 Opened 21 years ago Closed 21 years ago

Link buttons incorrectly displayed in a jumble at the right of the "search mozilla" form box

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 271990

People

(Reporter: djackson, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041203 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041203 Mozilla 1.8a6 incorrectly displays the mozilla home page at http://www.mozilla.org/. The "Developers", "Store", "Products" etc. buttons appear in a jumble off to the right of the "search mozilla" form box. This page was displayed correctly in 1.8a5. Clicking on one of the buttons also does not take you to the specified URL, but rather returns a version of the mozilla home page with the buttons rearranged. Clicking the rearranged buttons does link to the specified URLs. Reproducible: Always Steps to Reproduce: 1.Update to 1.8a6 2.open http://www.mozilla.org/ 3.click on "Developers" button Actual Results: Buttons rearrange, but display stays on mozilla home page rather than changing to developers page. Expected Results: displayed the buttons correctly and linked to the expected pages
Downloads from the mozilla ftp sites also do not seem to work with 1.8a6 (the URL target for the 1.8a5 release seemed correct, but no download progress bar appeared when clicking the download link). I don't know if this is related to the display problems that inspired this bug report, but there is a common theme of links not working correctly.
The incorrect display problem also appears with the Dec. 2 version of 1.8a6 on a win2K machine.
As expected, when I reverted to the 1.8a5 released version I no longer see the display problems.
*** This bug has been marked as a duplicate of 271990 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.