Closed Bug 299800 Opened 19 years ago Closed 18 years ago

buttons not displayed

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Linux
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Michel.Peyrard, Unassigned)

References

()

Details

(Whiteboard: CLOSEME - 06/18)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

I cannot use firefox on the site http://www.amazon.fr because the buttons (sich
as "gO" for a search, or "order" to place an order do not show up at all.
Using konqueror on Linux, with KDE, everything works fine.

Reproducible: Always

Steps to Reproduce:
1.connect to the site
2.observe the top of the screen. There is a form for search. 
3. It does not display a "go" button while it does with konqueror

Actual Results:  
Form for search without a button to start the search

Expected Results:  
The search does work if I press return, but for other parts of the site, the
absence of a button is more dramatic (for instance to order a book after finding
it) because there is no way to perform the action.

I know that problems with buttons have been reported, but I cannot determine if
they are similar (for instance I do not know if the missing button is a "java"
button).

I call it major because Firefox is completely useless on this site (and pobably
others?)
WFM - 1 day trunk build old. MacOS-X Tiger.

Are you using any 3rd party theme ? Any Extension ?
Michel, do you see this reported error also on a recent Firefox release like Firefox 2.0.0.4 ? If so, can you try if its working in Firefox Safe Mode http://kb.mozillazine.org/Safe_Mode ?
Whiteboard: CLOSEME - 06/18
Version: unspecified → 1.0 Branch
WORKSFORME as well. Resolving as such.

If you can still reproduce using Firefox 2.0.0.4 or later with a clean profile, please comment in this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.