[webshell]Unable to reproduce page containing search info

VERIFIED FIXED in M18

Status

()

P1
normal
VERIFIED FIXED
20 years ago
10 years ago

People

(Reporter: jcarpenter0524, Assigned: radha)

Tracking

({top100})

Trunk
x86
Windows NT
top100
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nsbeta2+][PDT-], URL)

(Reporter)

Description

20 years ago
- Searched for book at amazon.com
- backed up through selections
- While backing up through several pages, I ended up with the following message:

"Browser Bug?
It would appear that the web browser you are using,
Mozilla/4.05 [en] (Win95; I),
does not know how to re-submit forms correctly when you try to reload
a page.  If you want to reload the page you were on, try using your
browser's BACK button or command to go back to the previous page,
and resubmit the form yourself, instead of using RELOAD."

I was not using reload, but was in fact using the back button.
(Reporter)

Updated

20 years ago
Summary: browser unable to reproduce page with search info → browser unable to reproduce page containing search info

Updated

20 years ago
Assignee: michaelp → pollmann
Component: Rendering → Form Submission

Updated

20 years ago
Assignee: pollmann → gagan

Comment 1

20 years ago
I just checked with nglayout and verified this bug.  Strange that our User Agent
is telling sites we are 4.05, eh?

Gagan & Raman, this sounds like it might be a netlib or cache bug - is this the
case?  If not, can you give me any pointers on it?  thanks

Updated

20 years ago
Status: NEW → ASSIGNED
Component: Form Submission → Networking Library

Comment 2

20 years ago
Looks like a good candidate for post_data test in Netlib.

Comment 3

20 years ago
Setting all current Open/Normal to M4.

Comment 4

20 years ago
setting paulmac as QA contact for all gagan's bugs (sorry for the spam)

Updated

20 years ago
Target Milestone: M4 → M6

Comment 5

20 years ago
Marking till Necko lands...

Comment 6

20 years ago
Per DP's suggestion marking these till M8. Though Necko lands with M7, we will
be able to verify it for M8.

Comment 7

20 years ago
I'm moving this to target M9, Necko will be enabled somewhere during late M8 or
early M9.  We will need to get on this and it cannot be postponed past the M9
milestone.

Comment 8

20 years ago
Changing all Networking Library/Browser bugs to Networking-Core component for
Browser.

Occasionally, Bugzilla will burp and cause Verified bugs to reopen when I do
this in a bulk change.  If this happens, I will fix. ;-)

Updated

19 years ago
Summary: browser unable to reproduce page containing search info → NECKO: browser unable to reproduce page containing search info
Target Milestone: M9 → M10

Comment 9

19 years ago
Pl. verify with Necko. If the search is doing some posting then this may not
work till Posting in Necko is up and running.

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Whiteboard: waiting for posting

Comment 10

19 years ago
this can not be tested until posting exists. Will mark resolved then try to
verify when posting is available.

Updated

19 years ago
Whiteboard: waiting for posting → waiting for cache

Comment 11

19 years ago
actually, I don't think that this can be verified until we have a working cache

Updated

19 years ago
Whiteboard: waiting for cache → waiting for cache (M10)

Updated

19 years ago
Whiteboard: waiting for cache (M10) → waiting for cache (M11)

Updated

19 years ago
Status: RESOLVED → REOPENED

Updated

19 years ago
Assignee: gagan → fur
Status: REOPENED → NEW
Summary: NECKO: browser unable to reproduce page containing search info → [DOGFOOD] NECKO: browser unable to reproduce page containing search info

Updated

19 years ago
Resolution: FIXED → ---

Comment 12

19 years ago
Re-opening as this is still occuring. This may be a duplicate of another bug,
but I'm not sure if this is cache or what. Fur?

To duplicate:

1. Goto www.amazon.com
2. Under search, put in 'furman' and click go
3. Click on the elina furman link
4. Hit the back button

Results: You will get the error message that says your browser doesn't know how
to resubmit forms when loading a page.

Marking Dogfood as this happens on lots if not all pages with form submission
results (like search pages).

Comment 13

19 years ago
Re-submission of form data to the server during back/forward is related to
session history, not cache.  Sounds like this is a dup of 8241 or vice-versa.

Updated

19 years ago
Blocks: 12651

Updated

19 years ago
Assignee: fur → raman

Comment 14

19 years ago
Okay, I made 12651 dependent on this bug, and gave back to raman. I will leave
it as DOGFOOD and see what the PDT gods say.

Updated

19 years ago
Whiteboard: waiting for cache (M11) → [PDT+]waiting for cache (M11)

Comment 15

19 years ago
Putting on PDT+ radar.

Updated

19 years ago
Target Milestone: M10

Comment 16

19 years ago
removing M10 TFV

Updated

19 years ago
Summary: [DOGFOOD] NECKO: browser unable to reproduce page containing search info → [DOGFOOD] Unable to reproduce page containing search info

Comment 17

19 years ago
removing NECKO from summary, that's default now.

Updated

19 years ago
Assignee: raman → radha

Comment 18

19 years ago
raman doesn't work here anymore. Since fur suggested that this is a possible dup
for 8241, I'll reassign this to the owner of that bug.
Status: NEW → ASSIGNED
Component: Networking-Core → Browser-General
Target Milestone: M12

Updated

19 years ago
Depends on: 13374
Whiteboard: [PDT+]waiting for cache (M11) → [PDT+] 12/17??? completion

Comment 19

19 years ago
Added dependency on Webshell work, bug #13374.  Can we get this completed enough
for dogfood before 12/17?
I need to be able to get/set Post data from webshell to fix this. That will not
happen in the existing webshell. I have to wait until new docshell to fix this.
Need redesigned webshell to fix this.
Depends on: 18804
Summary: [DOGFOOD] Unable to reproduce page containing search info → [DOGFOOD][webshell]Unable to reproduce page containing search info

Updated

19 years ago
Priority: P2 → P1
Whiteboard: [PDT+] 12/17??? completion → [PDT+] Post webshell landing completion

Comment 22

19 years ago
Is this bug a dup of other history bugs?  Do you know when the piece of webshell
you need is landing?

Updated

19 years ago
Target Milestone: M12 → M13

Comment 23

19 years ago
Moving to M13.
This is dependant on some other History bugs but not a dup of any AFAIK. Early
next week is what I hear Travis.

Updated

19 years ago
Whiteboard: [PDT+] Post webshell landing completion → Post webshell landing completion

Comment 25

19 years ago
Removing PDT+ status because it's obvious we're not gonna hold up dogfood for
this.

Updated

19 years ago
Whiteboard: Post webshell landing completion → [PDT-]Post webshell landing completion

Comment 26

19 years ago
Putting on PDT- radar.  spoke with don, enough of this is working at this time.

Updated

19 years ago
QA Contact: paulmac → claudius

Comment 27

19 years ago
PDT asked me to check this out, it still occurs with 12/15 M12 candidate builds.

To duplicate just go to amazon.com, click on books, search on Orson Scott Card,
click on Ender's Shadow, and press back button. You will get the error.

To me this is borderline PDT+. It is a bit annoying.

setting claudius as qa contact

Updated

19 years ago
Blocks: 22176

Updated

19 years ago
No longer blocks: 12651

Updated

19 years ago
Summary: [DOGFOOD][webshell]Unable to reproduce page containing search info → [webshell]Unable to reproduce page containing search info
Whiteboard: [PDT-]Post webshell landing completion

Comment 28

19 years ago
Re-summarized.
Depends on: 17685
This s'd be fixed automatically when 17685 is fixed. I haven't marked this as a
dup of 17685 because there seem to be some good info on both. In essence, when
17685 is fixed, this could be marked as fixed.

Updated

19 years ago
Target Milestone: M13 → M14

Comment 30

19 years ago
Moving all to M14 (for webshell changes that are being deferred till M14 rather
than destabilize M13).

Comment 31

19 years ago
Marking as beta1.
Keywords: beta1

Comment 32

19 years ago
Putting on PDT+ radar for beta1.
Keywords: top100
Whiteboard: [PDT+]

Comment 33

19 years ago
This would be nice to fix, but it's not a beta stopper. clearing PDT+ status.
Whiteboard: [PDT+]

Comment 34

19 years ago
I imagine since the pdt+ was cleared but the beta1 keyword is still there and there's no minus this will just get reviewed again. 
Just know that this bug and bug 17685 travel together and bug 17685 has been established as PDT+. I would think this is a 
major annoyance in the case of a long form or a form with a large text field suitable for entering much info, like this very page.

Comment 35

19 years ago
Don, jevering would like you to see who could work on this...before you burn his 
car :)
Whiteboard: [PDT+]

Comment 36

19 years ago
Bill actually owns Radha's bugs while she's on sabbatical ...

Comment 37

19 years ago
Chriss already cleared the PDT+ once on this.  Bill Law already has a number of
other PDT+ bugs.  There has been no activity on this bug for the past 19 days.
Clearing PDT+ again
Whiteboard: [PDT+]

Comment 38

19 years ago
Putting on PDT- radar for beta1.
Whiteboard: [PDT-]
*** Bug 30252 has been marked as a duplicate of this bug. ***

Comment 40

19 years ago
how can this be open when bug 17685 is verified fixed? Aren't they closely related?
Component: Browser-General → History
Moving to M15...
Target Milestone: M14 → M15

Comment 42

19 years ago
Move to M16 for now ...
Target Milestone: M15 → M16

Updated

19 years ago
Keywords: beta1 → nsbeta2

Comment 43

19 years ago
In light of the webshell ans SH changes I've reevaluted this bug and it still exists as originally reported in the 2000042109 builds. 
marking nsbeta2, assuming we've raised the bar since beta1.

Comment 44

19 years ago
Putting on [nsbeta2+] radar for beta2 fix. 
Whiteboard: [PDT-] → [nsbeta2+][PDT-]
Depends on: 39668

Comment 45

19 years ago
Move to M18.
Target Milestone: M16 → M18
Fix in hand. Shall checkin once tree opens
Target Milestone: M18 → M16
checked in fix
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago19 years ago
Target Milestone: M16 → M18

Updated

19 years ago
No longer blocks: 22176

Comment 48

19 years ago
VERIFIED Fixed with 2000070708 builds
Status: RESOLVED → VERIFIED
mid-air collision ? / bugzilla cleanup
Reopening (current State: verfied and no resolution)
Status: VERIFIED → REOPENED
fixed
Status: REOPENED → RESOLVED
Last Resolved: 19 years ago18 years ago
Resolution: --- → FIXED
verified
Status: RESOLVED → VERIFIED

Updated

10 years ago
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
You need to log in before you can comment on or make changes to this bug.