Bug 176186 - offsite.js is missing for /usr/share/doc/HTML/index.html
Summary: offsite.js is missing for /usr/share/doc/HTML/index.html
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: release-notes
Version: devel
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Release Notes Tracker
QA Contact: Karsten Wade
URL: /usr/share/doc/HTML/index.html
Whiteboard:
Depends On:
Blocks: FC5Blocker fc5-relnotes-traqr
TreeView+ depends on / blocked
 
Reported: 2005-12-19 21:12 UTC by Yan Morin
Modified: 2007-04-18 17:35 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-28 07:20:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Yan Morin 2005-12-19 21:12:09 UTC
Description of problem:  
/usr/share/doc/HTML/index.html use offsite.js file and OffSite() javascript 
function. 
  
Version-Release number of selected component (if applicable):  
4-2  
  
How reproducible:  
always  
  
Steps to Reproduce:  
1. open the file with your browser 
2. check javascript error (javascript console) 
 
    
Actual results:  
file not present, error OffSite() not declared  
  
Expected results:  
A information page without error

Comment 1 Karsten Wade 2006-01-25 20:51:01 UTC
I'm not sure yet what this is about.  Thanks for catching the error, and we'll
work on fixing this for test3.

Setting to block appropriate tracking bug.


Comment 2 Karsten Wade 2006-02-15 21:01:27 UTC
Tracking this fix for FC5 final.

Comment 3 Karsten Wade 2006-02-28 06:43:00 UTC
This file:

cvs.fedora:fedora-release/indexhtml-head

is looking for offsite.js, but it is not there.

Should we:

i.  Replace offsite.js
ii. Remove the call to offsite.js



Comment 4 Karsten Wade 2006-02-28 07:20:54 UTC
The reference is now commented out, which should prevent the JavaScript error. 
I didn't want to remove the reference entirely, because I don't know the history
of the offsite.js file.

Reopen this bug if you encounter the same error in final notes, but you
shouldn't. :)


Note You need to log in before you can comment on or make changes to this bug.