Consider use of BASE tag in show_bug.cgi (or all files)

NEW
Unassigned

Status

()

P4
enhancement
17 years ago
9 years ago

People

(Reporter: ddkilzer, Unassigned)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
Some discussion in Bug 133283 lead to the suggestion that it might
be better (or more efficient) to use a BASE tag in the HEAD section
of output HTML so that saved HTML output from a Bugzilla
installation would be usable when loaded into a web page (Bug 53951).

http://bugzilla.mozilla.org/show_bug.cgi?id=133283#c9

Gerv noted in the next comment that this should be looked at in a
future release of Bugzilla, not 2.16, hence this bug.
(Reporter)

Comment 1

17 years ago
HTML 4.01 definition of the BASE tag:

http://www.w3.org/TR/html401/struct/links.html#edef-BASE
Summary: Consider use of BASE tag in show_bug.cgi (or all files) → Consider use of BASE tag in show_bug.cgi (or all files)
Priority: -- → P4
Target Milestone: --- → Bugzilla 2.18

Updated

15 years ago
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.
Assignee: justdave → general
QA Contact: mattyt-bugzilla → default-qa

Comment 4

13 years ago
The trunk is now frozen to prepare Bugzilla 2.22. Only bug fixes are accepted, no enhancement bugs. As this bug has a pretty low activity (especially from the assignee), it's retargetted to ---. If you want to work on it and you think you can have it fixed for 2.24, please retarget it accordingly (to 2.24).
Target Milestone: Bugzilla 2.22 → ---

Updated

13 years ago
Assignee: general → bugzilla-mozilla
Target Milestone: --- → Bugzilla 2.24
Version: 2.15 → 2.20

Comment 5

13 years ago
Created attachment 220447 [details] [diff] [review]
Patch v1: Bugzilla HEAD 2006-05-01

Notes:
 - does not set base href if urlbase is empty
 - creates self_url template variable (not 100% sure there isn't a better way to easily get Bugzilla.cgi.self_url without adding [% USE Bugzilla %] everywhere)
 - changes links to anchors to be prefixed with $self_url
Attachment #220447 - Flags: review?(wurblzap)
Maybe I'm getting the whole thing wrong... I expected to find
<base href="[% Bugzilla.cgi.self_url %]"> added to header.html.tmpl, and no further changes. Olav, can you tell me what I'm missing?

Comment 7

13 years ago
Comment on attachment 220447 [details] [diff] [review]
Patch v1: Bugzilla HEAD 2006-05-01

>Index: template/en/default/global/header.html.tmpl

>+    [% IF Param('urlbase') %]
>+      <base href="[% Param("urlbase") %]">
>+    [% END %]

That's not the desired behavior if SSLbase is used. Moreover, I think all links should be relative, probably. Please answer Marc's question.
Attachment #220447 - Flags: review?(wurblzap) → review-

Comment 8

12 years ago
This bug is retargetted to Bugzilla 3.2 for one of the following reasons:

- it has no assignee (except the default one)
- we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1)
- it's not a blocker

If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0.

If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug.

If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".
Target Milestone: Bugzilla 3.0 → Bugzilla 3.2

Comment 9

11 years ago
Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.
Target Milestone: Bugzilla 3.2 → ---

Updated

9 years ago
Assignee: bugzilla-mozilla → general
You need to log in before you can comment on or make changes to this bug.