Closed
Bug 214765
Opened 22 years ago
Closed 15 years ago
Loss of history if groupmark contains www.journaldunet.com (caused by new "replace" behaviour for groupmarks)
Categories
(SeaMonkey :: Tabbed Browser, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: pascalc, Unassigned)
References
()
Details
(Keywords: dataloss)
build 2003073110 WinXP
1 create a groupmark in which http://www.journaldunet.com/ is present
2 visit a page
3 click on the new groupmark
4 click on the different tabs
actual result : back button is greyed out, loss of previous history
expected result : we should be able to get back to the pages we were at before
clicking the groupmark
-> dataloss
Caused by bug 203960
i think this one is a subset of bug 214905 and should be duplicated to that one.
Or do you mean something else Pascal?
Reporter | ||
Comment 2•21 years ago
|
||
It is different in fact, there is one step less than in 214905 and if you don't
have journaldunet.com in the groupmark, it works.
Assignee | ||
Updated•16 years ago
|
Product: Core → SeaMonkey
Updated•16 years ago
|
Assignee: jag → nobody
QA Contact: pmac → tabbed-browser
Comment 3•16 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 4•15 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
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•