56877 - Meta=GENERATOR not updated; Meta Author tag not updated

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[Gagan]

I had a page saved as a template from a 4.74 version that I edited in 6.0

The <meta name="GENERATOR" content="Mozilla/4.74 [en] (WinNT; U) [Netscape]">
was never updated to correctly reflect 6.0

Comment 1

[rubydoo123]

good catch gagan! but this will have to wait until after rtm

Comment 2

[Kathleen :Brade]

The current thinking on this bug is that we should have an author and an editor
tag (editor being the last/current person who is revising it; author being the
first person who created the file).

We should similarly have the original generator as well as the last-editing with
generator.

We may also want to add the date created and date last revised as CDATA or in
the head or ?

Comment 3

[kinmoz]

So was there a decision on the exact set of tags we want to write out/modify?

Comment 4

[Syd Logan]

spam composer change

Comment 5

[Kathleen :Brade]

Beppe--as w3c rep, can you recommend what we should use when revising a document?  
Should we just replace the meta tags or insert new meta tags and leave the 
existing ones as is?

Comment 6

[Syd Logan]

Agreed, removing EDITORBASE

Comment 7

[Asa Dotzler [:asa]]

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)

Comment 8

[rubydoo123]

removing myself from the cc list

Comment 9

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

Taking bug's ownership.

Comment 10

[Kevin McCluskey (gone)]

nsbeta1-. We need to go after more serious issues first.

Comment 11

[Matti]

Two years later this issue hasn't been fixed.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040725

Comment 12

[Matti]

I've also discovered that Composer doesn't insert the generator meta tag into a
new file, either.

Comment 13

[Gérard Talbot]

*** Bug 224418 has been marked as a duplicate of this bug. ***

Comment 14

[Gérard Talbot]

IMO, the best thing to do would be to use Dublin Core Metadata tags 
(see  http://www.ietf.org/rfc/rfc2731.txt )
for the data of the related issues covered by this bug: revision, author, date
first created, date modified, generator, etc.
Maybe:
<meta name="DC.Editor" content="Mozilla 1.8 Composer">
or
<meta name="DC.Generator" content="Mozilla 1.8 Composer">

http://dublincore.org/documents/2002/10/06/current-elements/
http://www.w3.org/2000/Talks/1019-rdf-poly/slide16-0.html

If Composer is going to edit such metatags, then it should
conform and comply to known and widely established norms, standards.

Comment 15

[Robert Kaiser]

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

Comment 16

[Robert Kaiser]

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

Comment 17

[Robert Kaiser]

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

Comment 18

[Robert Kaiser]

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

Comment 19

[Robert Kaiser]

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

Comment 20

[Robert Kaiser]

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