Closed
Bug 56276
Opened 25 years ago
Closed 25 years ago
Xul file does not load the banner
Categories
(Core :: XML, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: teruko, Assigned: alecf)
References
()
Details
Attachments
(1 file)
3.78 KB,
text/xul
|
Details |
This is found by using Alis Translation.
During the PR3, their banner on the top of the Alis Translation solution page
after you click on gist button.
I got the test pages from Alis.
Steps of reproduce
1. Go to above URL
http://www.mozilla.org/ page is displayed.
The banner on the top is not displayed.
Tested 2000-10-11-08 MN6 build.
Reporter | ||
Updated•25 years ago
|
QA Contact: petersen → teruko
Assignee | ||
Comment 1•25 years ago
|
||
Wheres the stylesheet for this page? there's a line in
ns_toolbar_frames_ui.ja.xul that says:
<?xml-stylesheet href="/alis.ja.css?AlisTargetHost=localhost" type="text/css"?>
does this too live in a different location?
Assignee | ||
Comment 2•25 years ago
|
||
yep, sure enough if I just change the stylesheet to "chrome://navigator/skin/"
this XUL loads ok.. but you're also using <titledbuttons> which are depricated
and appearantly don't work anymore either.
Uploading a repaired XUL file now
Assignee | ||
Comment 3•25 years ago
|
||
Assignee | ||
Comment 4•25 years ago
|
||
actually, I'm noticing that the image URLs in this file are absolute URLs, so
I'm guessing that this file actually exists on a remote server somewhere, and
that the stylesheet was in place.
So I think the thing that actually fixed it was to use <button> instead of
<titledbutton>
Comment 5•25 years ago
|
||
Alecf - Thanks for the assist.
Reporter | ||
Comment 6•25 years ago
|
||
thanks. I close this bug.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 7•25 years ago
|
||
reassigning to me and re-closing (hey, I did the legwork :))
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 9•25 years ago
|
||
fixed.
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•