Closed Bug 336018 Opened 19 years ago Closed 19 years ago

Serve valid XHTML

Categories

(Bugzilla :: User Interface, defect)

Other
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 336019

People

(Reporter: frans.englich, Unassigned)

Details

User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux; en_US) KHTML/3.4.89 (like Gecko) Build Identifier: It would be great if all pages served from a Bugzilla setup was valid XHTML. Currently, it seems to be somekind of tag soup. What I more specifically suggests, is that each served page contains: * An XML prolog: <?xml encoding="UTF-8" version="1.0"?> * A DOCTYPE declaration. For example: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> * A correct element document: <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> The purpose of doing this is as follows. * How Bugzilla appears to your users is more clear, since it's well defined how web browsers should render it. Currently, they try to cope the best they can, interpret it the way /they/ think it's supposed to be done. * It renders faster * As one of the largest internet citizen, you'll improve the environment by promoting standards instead of breaking them * Again, a clearer product since encoding and locale is specified(and not only on the HTML level) * Better style/content separation, and better styling possibilities This will make a better Bugzilla, especially for things like accessibility software and small devices. I suggest XHTML in front of HTML, because the former is the future while the latter will fade away over time. XHTML also gives you the possibility to in the future serve compound documents, where meta data in RDF is embedded in the XHTML, for example. XHTML also means one can programatically process the documents with for example XSL-T -- that's how I discovered this. I also think you should make document validity part of your regression testing, since how Reproducible: Always
*** This bug has been marked as a duplicate of 336019 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.