Closed Bug 87420 Opened 23 years ago Closed 19 years ago

Pressing back on "create attachment".

Categories

(Bugzilla :: Attachments & Requests, defect, P3)

2.13
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: CodeMachine, Assigned: myk)

References

Details

When you get an error after the create attachment page, and you press back, you get the same error. You should go back to the attach page.
Matty, what brower do you use? I duplicated this with Netscape 4.76 Mac. However, I'm pretty convinced that it's a browser bug, and not Bugzilla. It works correctly in both iCab and Omniweb, so it sounds like a cache problem. If you can duplicate this in Mozilla, move this bug to tbe browser component, otherwise it needs to be marked invalid.
I can't reproduce this in Mozilla but I'd like us to work around it because it doesn't happen anywhere else. I'm assuming this occurs because both pages have exactly the same URL. This should be fairly easy to work around.
Target Milestone: --- → Bugzilla 2.16
Priority: -- → P3
-> Bugzilla product, Changing Bugs component, reassigning.
Assignee: tara → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: Bugzilla 2.13 → 2.13
Depends on: 98602
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Component: Creating/Changing Bugs → attachment and request management
Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being retargeted to 2.20 If you plan to act on one immediately, go ahead and pull it back to 2.18.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to nobody@bugzilla.org or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.
Target Milestone: Bugzilla 2.20 → ---
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.