Closed Bug 376311 Opened 18 years ago Closed 18 years ago

report broken website has no privacy policy or details to enter

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 373727

People

(Reporter: adman.com, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3) Gecko/20070322 GranParadiso/3.0a3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3) Gecko/20070322 GranParadiso/3.0a3 The first time, I submitted a "Report Broken Web Site" perfectly and worked, showing the proper screens. The next site I went to, and wanted to report it as broken, the dialog did not show up properly. There is no privacy policy, and only one step, e.g. no details can be entered, only a blank report submitted Reproducible: Always Steps to Reproduce: 1. Start Gran Paradiso/ Firefox 3.0a3 2. Go to any site 3. Click Help>Report Broken Web Site... Actual Results: the dialog did not show up properly. There is no privacy policy, and only one step, e.g. no details can be entered, only a blank report submitted. A screenshot is at http://adman.com.googlepages.com/errorshot1.gif , http://adman.com.googlepages.com/errorshot2.gif and http://adman.com.googlepages.com/errorshot3.gif. Expected Results: Shown the privacy policy, and give me space to enter details about the report Theme: macfoxIIgraphite about:buildconfig Build platform target i686-pc-cygwin Build tools Compiler Version Compiler flags $(CYGWIN_WRAPPER) cl 14.00.50727 -TC -nologo -W3 -Gy -Fd$(PDBFILE) $(CYGWIN_WRAPPER) cl 14.00.50727 -GR- -TP -nologo -Zc:wchar_t- -W3 -Gy -Fd$(PDBFILE) Configure arguments --enable-application=browser --enable-update-channel=beta --enable-optimize --disable-debug --disable-tests --enable-static --disable-shared --enable-svg --enable-canvas --enable-default-toolkit=cairo-windows --enable-update-packaging --with-branding=browser/branding/unofficial
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.