Publishing error dialog should not have a cancel button

RESOLVED EXPIRED

Status

SeaMonkey
Composer
--
minor
RESOLVED EXPIRED
15 years ago
8 years ago

People

(Reporter: timeless, Assigned: jag (Peter Annema))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
For fun i wrote the steps to reproduce this bug in the url.

Steps to get to the steps to reproduce: click the url link.
From there simply follow the steps listed.

imo when publishing fails the dialog should have some other button instead of
'cancel' and it definitely should not result in the intermediate continue/cancel
dialog.
(Reporter)

Comment 1

15 years ago
Created attachment 125565 [details]
picture

Comment 2

15 years ago
-->jag since he introduced this dialog
Assignee: composer → jaggernaut
OS: Windows 2000 → All
Hardware: PC → All

Comment 3

15 years ago
So what happens when publishing succeeds, and the dialog is kept open by the
checkbox? Presumably that code could be leveraged to resolve part of this bug.
For the rest of the bug, IMHO a publish failure should cancel the close.
Product: Browser → Seamonkey

Comment 4

9 years ago
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

Comment 5

8 years ago
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
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.