[MAGNOLIA-1086] use valid xhtml strict for all the generated html code Created: 27/Sep/06  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Fabrizio Giustina Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

a good task for 3.0.1: fix all the magnolia generated code in order to be valid xhtml 1.0 strict.

At this moment most of the UI uses valid xhtml code, but there are a few exception, especially lists
admin interface main page and list pages are actually broken if browsers switch to standard-compliant mode (which we should always use).

When anybody create a new page or gui component please make sure that:

  • the dtd used is:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    and NOT missing or html transitional or without a dtd (there is a big difference, a valid dtd makes browser change the rendering mode)
  • there are no errors in the generated code: please look at the firefox error console for css errors and use something like the firefox html validator extension [ http://users.skynet.be/mgueury/mozilla/ ] in order to check that there are no html errors


 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:23:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.