Closed Bug 115832 Opened 23 years ago Closed 14 years ago

File -> Edit Page -> not reposting data

Categories

(SeaMonkey :: Composer, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: donguana, Unassigned)

References

Details

From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (Windows NT 5.0; U)
BuildID:    20011217

Composer opens the file based on the URL and not based on what is displayed on 
the page. This makes it difficult to edit a page that was  submitted via a form 
(POST).


Reproducible: Always
Steps to Reproduce:
Go to any page containing a form and submit the form and then try to edit the 
result page. (form must be a POST). Use the File -> Edit Page from the menu.

Actual Results:  The editor opens the previous page containing the form and not 
the search results. 

Expected Results:  Expecting to edit the result page. Expecting that Mozilla 
would ask to  repost data before the edit.

Could this be related to bug 109785?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Severity: normal → enhancement
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Depends on: 40867
*** Bug 132770 has been marked as a duplicate of this bug. ***
*** Bug 149038 has been marked as a duplicate of this bug. ***
OS: Windows NT → All
Hardware: PC → All
reassign to new account
Assignee: syd → composer
Status: ASSIGNED → NEW
Product: Browser → Seamonkey
Assignee: composer → nobody
QA Contact: sujay → composer
Target Milestone: Future → ---
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.