Re: [PLIP-Advisories] [Plone] #9300: Well formed, valid XHTML

[Change notifications for Plone PLIPs on Trac.]

#9300: Well formed, valid XHTML
---+
 Reporter:  benglynn   |Owner:  benglynn
 Type:  PLIP   |   Status:  closed  
 Priority:  minor  |Milestone:  4.x 
Component:  Templates/CSS  |   Resolution:  wontfix 
 Keywords: |  
---+
Changes (by rossp):

  * status:  assigned => closed
  * resolution:  => wontfix


Comment:

 Superceded by #11300

-- 
Ticket URL: 
Plone 
Plone Enterprise Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
https://lists.plone.org/mailman/listinfo/plip-advisories

Re: [PLIP-Advisories] [Plone] #9300: Well formed, valid XHTML

[Change notifications for Plone PLIPs on Trac.]

#9300: Well formed, valid XHTML
---+
 Reporter:  benglynn   |Owner:  benglynn
 Type:  PLIP   |   Status:  assigned
 Priority:  minor  |Milestone:  4.x 
Component:  Templates/CSS  |   Resolution:  
 Keywords: |  
---+

Comment(by ldr):

 Adding XDV in front of Plone will ensure output is well formed XML. It
 won't help with the duplicate id issues though. I think those are mostly
 down to content viewlets using ids, which breaks in listings are multiple
 content viewlets end up being shown.

-- 
Ticket URL: 
Plone 
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories