You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by is...@cocoondev.org on 2004/12/20 02:29:29 UTC
[JIRA] Commented: (FOR-414) add @content to document document-v20.mod meta attribs
The following comment has been added to this issue:
Author: Ross Gardler
Created: Sun, 19 Dec 2004 7:29 PM
Body:
If we add the content attribute then we should really add all attributes from the meta-data attribute collection (see http://www.w3.org/TR/xhtml2/mod-metaAttributes.html#s_metaAttributesmodule)
The meta-data module is one scheduled to be included with the move to XHTML so I see no problem with this attribute being added, but do we need it? According to the XHTML spec, if the content attribute is missing from a meta element then the elemets contents are assumed to be its content (see above linked page). That is how things are working at the moment.
So do we need this patch? I'd prefer to see all the attributes on the above page added, rather than just some of them, but then if you have a strong use case I see no problem with it.
---------------------------------------------------------------------
View this comment:
http://issues.cocoondev.org//browse/FOR-414?page=comments#action_11952
---------------------------------------------------------------------
View the issue:
http://issues.cocoondev.org//browse/FOR-414
Here is an overview of the issue:
---------------------------------------------------------------------
Key: FOR-414
Summary: add @content to document document-v20.mod meta attribs
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Forrest
Components:
Core operations
Versions:
HEAD
Assignee:
Reporter: Sean Wheller
Created: Sun, 19 Dec 2004 12:43 PM
Updated: Sun, 19 Dec 2004 7:29 PM
Description:
Add content attribute to meta element.
<meta name="description" content="Free Open Source GNU/Linux Training Materials"/>
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: [JIRA] Commented: (FOR-414) add @content to document document-v20.mod meta attribs
Posted by Sean Wheller <se...@inwords.co.za>.
On Monday 20 December 2004 03:29, issues@cocoondev.org wrote:
> So do we need this patch? I'd prefer to see all the attributes on the above
> page added, rather than just some of them, but then if you have a strong
> use case I see no problem with it.
Most people prefer to use meta an an open element. At a minimum they use name
and content attributes.
--
Sean Wheller
Technical Author
sean@inwords.co.za
084-854-9408
http://www.inwords.co.za
Re: [JIRA] Commented: (FOR-414) add @content to document document-v20.mod
meta attribs
Posted by Ross Gardler <rg...@apache.org>.
Sean Wheller wrote:
> On Monday 20 December 2004 03:29, issues@cocoondev.org wrote:
>
>>If we add the content attribute then we should really add all attributes
>>from the meta-data attribute collection
>
>
> Ross,
>
> Will this do
My comment on the issue was meant as a question to all, do we need the
@content attribute and if we do then should we consider the other
attributes?
Ross
Re: [JIRA] Commented: (FOR-414) add @content to document document-v20.mod meta attribs
Posted by Sean Wheller <se...@inwords.co.za>.
On Monday 20 December 2004 03:29, issues@cocoondev.org wrote:
> If we add the content attribute then we should really add all attributes
> from the meta-data attribute collection
Ross,
Will this do
<!ATTLIST meta
about CDATA #IMPLIED
content CDATA #IMPLIED
datatype CDATA #IMPLIED
name NMTOKEN #REQUIRED
property CDATA #IMPLIED
rel CDATA #IMPLIED
resource CDATA #IMPLIED
restype CDATA #IMPLIED
rev CDATA #IMPLIED
%common.att;
>
--
Sean Wheller
Technical Author
sean@inwords.co.za
084-854-9408
http://www.inwords.co.za