Bug 171 – Script error in Fishbone Skin

Bug 171 - Script error in Fishbone Skin

Summary:

Script error in Fishbone Skin

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Skins
Version:	unspecified
Platform:	PC Windows (legacy)

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	KDF

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2004-01-27 13:42 UTC by Pascal Berger
Modified:	2008-09-15 14:37 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Pascal Berger 2004-01-27 13:42:50 UTC

I get an error with the Fishbone Skin (v2004-01-26) on the Squeezebox Home site:

Line: 108
Character: 1
Error: 'top.document.getElementById(...)' is Null or not an object
Code: 0
URL:
http://localhost:9000/status_header.html?player=00%3a04%3a20%3a05%3a08%3aa6%start=%refresh=1

(Note: Error message is translated from german. In english there could be a
slightly different wording)

Comment 1 KDF 2004-01-27 15:08:13 UTC

I can't reproduce this?  Do you have html caching on?  If you upgraded, turn it
off, refresh, then turn back on.  Which browser is this?

Comment 2 Pascal Berger 2004-01-28 00:35:55 UTC

I'll test this as soon as I'm back at home. It was with the supplied Windows
application (IE, I think)

Comment 3 KDF 2004-01-28 01:06:47 UTC

reproduced it.  This occurs only when changing the skin from another to
Fishbone.  The skin has not been fully activated with the reload link, so the
status side is still using the former skin.  This will cause an error, becuase
the frame is not properly named yet.  You must refresh the window or click on
the link contained in: "Click here to refresh and see the new skin."

Comment 4 KDF 2004-01-28 20:53:54 UTC

just committed a patch to cvs.  it notices the missing frame and triggers a full
reload before the error can occur.

Comment 5 Chris Owens 2006-06-16 14:40:11 UTC

There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.