Closed
Bug 301140
Opened 20 years ago
Closed 20 years ago
cloning an event changes lastModifiedTime
Categories
(Calendar :: Internal Components, defect)
Calendar
Internal Components
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mvl, Assigned: mvl)
Details
Attachments
(1 file)
958 bytes,
patch
|
shaver
:
first-review+
|
Details | Diff | Splinter Review |
When cloning an event, the lastModifiedTime of both the original and the clone
are set to the current time.
The original should never change, and i don't thing the clone should change either.
Assignee | ||
Comment 1•20 years ago
|
||
The problem seems to be that stamptime is changed when cloning. I don't think
it is needed, but vlad added it for full recurrence support. Vlad, is it really
needed? Do you use the stamp anywhere?
Assignee | ||
Updated•20 years ago
|
Attachment #189631 -
Flags: first-review?(vladimir) → first-review?(shaver)
Comment 2•20 years ago
|
||
Comment on attachment 189631 [details] [diff] [review]
don't set stamptime
r=shaver
Attachment #189631 -
Flags: first-review?(shaver) → first-review+
Assignee | ||
Comment 3•20 years ago
|
||
patch checked in.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•