Closed Bug 173027 Opened 23 years ago Closed 23 years ago

code-error.html.tmpl misses a </em>

Categories

(Bugzilla :: User Interface, defect)

2.17
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 2.18

People

(Reporter: burnus, Assigned: gerv)

Details

- The component <em>[% variables.component FILTER html %] does not exist + The component <em>[% variables.component FILTER html %]</em> does not exist Additional I'd like to ask whether all errors should have an uniq title (as they do in user-error.html.tmpl) or not ("Internal Error" in code-error.html.tmpl). In code-error.html.tmpl only 6/33 errors have a title.
I'll fix this tonight - I assume I have your r= on a change which adds a </em>? Code Errors don't need a title, really - because they are infrequently encountered, and the body should contain all the necessary information. Adding titles just makes more work - and there's some value in code errors having a consistent title, actually. So maybe we should remove the titles we have. Gerv
> I'll fix this tonight - I assume I have your r= on a change which adds a </em>? Yes of cause. Or take my minimal patch and give me a r= ;-) This is "flag_type_component_nonexistent" by the way. > Code Errors don't need a title, really - because they are infrequently > encountered, and the body should contain all the necessary information. Adding > titles just makes more work - and there's some value in code errors having a > consistent title, actually. So maybe we should remove the titles we have. I think the titles look ok, but I don't mind to review a patch which removes those. Is the aaa_example_error_tag still needed?
Fixed. Checking in template/en/default/global/code-error.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/global/code-error.html.tmpl,v <-- code-error.html.tmpl new revision: 1.17; previous revision: 1.16 done Gerv
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Target Milestone: --- → Bugzilla 2.18
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.