Bug 9 - [Chameleon Widget] spinner image never disappears
: [Chameleon Widget] spinner image never disappears
Status: RESOLVED WONTFIX
: Chameleon
Core
: 1.99
: Macintosh MacOS X
: P1 major
: 1.99 beta 4
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2003-07-09 00:30 by
Modified: 2004-12-02 21:26 (History)


Attachments


Note

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


Description From 2003-07-09 00:30:15
When chameleon loads, the spinner image (loading map) never goes away on the 
following browser:

Safari 1.0 (v85) under Mac OS X 10.2.6
------- Comment #1 From 2004-04-07 12:28:14 -------
Safari (and Konquorer based browsers) are not officially supported by Chameleon.
 We did some testing and discovered that the early versions of Konquorer had
very incomplete javascript implementations.  I would expect that we will see
Konquorer working sometime in the future but we will not be attempting to make
Chameleon compatible with it until it is apparent that it is stable and
reasonably complete.

reassigning to Zak for monitoring.
------- Comment #2 From 2004-04-07 21:56:14 -------
Could Chameleon at least produce a warning/error when the page loads in an
incompatible browser?  If visitors to a site are informed that the problem is
that their browser is not supported, then at least most of them can use a
different browser, that would be less frustrating than getting a broken page I
think.
------- Comment #3 From 2004-04-08 08:33:36 -------
yes, I suppose it could ... browser detection may not be 100% though ... I'll
file a separate enhancement for this issue.
------- Comment #4 From 2004-04-08 08:35:30 -------
updated version to 1.99
------- Comment #5 From 2004-07-07 17:05:26 -------
Changed target to 1.99 Final.
------- Comment #6 From 2004-07-08 09:12:37 -------
Couldn't this be targetted for an RC not the Final?
------- Comment #7 From 2004-11-29 09:16:37 -------
In my testing this problem no longer occurs in Safari 1.2 and above. Note that
Safari has been forked 
into a OS X 10.2.x version (1.0) and a OS X 10.3.x version (1.2). Bug fixes are
supposedly applied to 
both. However, I haven't been able to test this on an up-to-date 1.0 version.
Marking as WONTFIX.