Closed Bug 546838 (bz-html5) Opened 10 years ago Closed 6 years ago

Upgrade Bugzilla to HTML5


(Bugzilla :: User Interface, enhancement)

Not set



Bugzilla 5.0


(Reporter: GPHemsley, Assigned: LpSolit)




(Keywords: html5, meta, student-project)


(1 file, 2 obsolete files)

(This is a pseudo-meta bug, meaning that it serves double duty.)

I think it's time to bring Bugzilla into the 21st century and switch the templates to HTML5.

And, to clear up any confusion, this proposal does not create any backwards-compatibility problems. HTML5 is more than fancy new tags. It also codifies and clarifies what browsers should have been doing with HTML4. In particular, that means IE6 will not suddenly break as a result of this switch. (At least, not intentionally.) In fact, as Hixie himself has stated, IE6 technically supports more of HTML5 than it does of HTML4, due to the addition of previously-proprietary features to HTML5.

So this bug serves as the home base for the Bugzilla upgrade to HTML5. It may contain its own patches. However, it can also depend on smaller-scope HTML5-related bugs, like bug 546353.
Okay. File specific bugs and explain specifically what you want to do on each of those bugs, and we can take each of those decisions separately.
Keywords: meta
Alias: bugzilla-html5 → bz-html5
Attached patch Step Number One (obsolete) — Splinter Review
This switches over or adds the HTML5 doctype to all templates with <html> (except the XUL one).
For reference, I don't want to switch the DOCTYPE until there's actually some HTML5 in use.
Depends on: 547171
Keywords: student-project
Target Milestone: Bugzilla 4.0 → Bugzilla 5.0
Blocks: 686333
Duplicate of this bug: 767707
We are going to branch for Bugzilla 4.4 next week and this bug is too invasive or too risky to be accepted for 4.4 at this point. The target milestone is set to 5.0 which is our next major release.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else on time for 5.0.
Target Milestone: Bugzilla 4.4 → Bugzilla 5.0
Blocks: 888731
Attached patch patch, v2 (obsolete) — Splinter Review
We are ready to shift to HTML5.
Assignee: ui → LpSolit
Attachment #427539 - Attachment is obsolete: true
Attachment #8356757 - Flags: review?(justdave)
Attached patch patch, v2.1Splinter Review
Oops, I removed [% DEFAULT title = ... %] unintentionally.
Attachment #8356757 - Attachment is obsolete: true
Attachment #8356757 - Flags: review?(justdave)
Attachment #8356760 - Flags: review?(justdave)
Keywords: relnote
Comment on attachment 8356760 [details] [diff] [review]
patch, v2.1

Attachment #8356760 - Flags: review?(justdave) → review+
I think we missed a few things but they'll be easier to find once the doctype is set correctly so the validators will notice them.
Flags: approval+
Committing to: bzr+ssh://
modified template/en/default/rest.html.tmpl
modified template/en/default/attachment/diff-header.html.tmpl
modified template/en/default/global/header.html.tmpl
modified template/en/default/list/list-simple.html.tmpl
modified template/en/default/list/server-push.html.tmpl
modified template/en/default/reports/duplicates-simple.html.tmpl
modified template/en/default/reports/report-simple.html.tmpl
modified template/en/default/setup/
modified template/en/default/whine/mail.html.tmpl
Committed revision 8856.
Closed: 6 years ago
Resolution: --- → FIXED
Blocks: 673385
Added to relnotes for 5.0rc1.
Keywords: relnote
(In reply to Dave Miller [:justdave] ( from comment #9)
> I think we missed a few things but they'll be easier to find once the
> doctype is set correctly so the validators will notice them.
Resolved fixed, and 19 months later this site still uses the legacy DOCTYPE...
(In reply to reelix from comment #12)
> Resolved fixed, and 19 months later this site still uses the legacy

That is because this site runs Bugzilla version 4.x, while you can see that the Target Milestone of this ticket is set to Bugzilla version 5.0. Hence no contradiction.
You need to log in before you can comment on or make changes to this bug.