Bug 15150 - Antem.Manager.RegisterStartUpScript
Summary: Antem.Manager.RegisterStartUpScript
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-06 02:35 PDT by Pierre Milburn
Modified: 2017-03-20 19:35 PDT (History)
2 users (show)

See Also:

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 Pierre Milburn 2007-09-06 02:35:54 PDT 
I have a problem with Safari 2.0 to 2.4 using the function :

Anthem.Manager.RegisterStartupScript(Page,"key","closelightbox",true.

This functions works fine in IE, Firefox and Opera but not in Safari.

The sentence puts a javascript function on the page from server side code in .NET Visual Studio 2005.

Anthem is a free source Ajax library (1.5.1)

/Pierre
Comment 1 Mark Rowe (bdash) 2007-09-06 02:48:51 PDT 
Can you please provide a URL that demonstrates the issue, and clarify which versions of WebKit you are seeing the problem with.  You mention "Safari 2.0 to 2.4", but there is no Safari 2.4.
Comment 2 Pierre Milburn 2007-09-06 04:47:33 PDT 
(In reply to comment #1)
> Can you please provide a URL that demonstrates the issue, and clarify which
> versions of WebKit you are seeing the problem with.  You mention "Safari 2.0 to
> 2.4", but there is no Safari 2.4.

(In reply to comment #1)
> Can you please provide a URL that demonstrates the issue, and clarify which
> versions of WebKit you are seeing the problem with.  You mention "Safari 2.0 to
> 2.4", but there is no Safari 2.4.

That's true, Safari is 2.0.4

WebKit version r25353

I have also tried Safari 3.3 public beta in Mac with the same Webkit and it works fine. 

Can I see the webkit number from the browser i am running?

/Pierre
Comment 3 Mark Rowe (bdash) 2007-09-06 05:16:23 PDT 
Please read the version numbers you are reporting closely.  Safari 3.3 does not exist, so I assume you are referring to Safari 3.0.3.

What URL can be used to reproduce this issue?
Comment 4 Pierre Milburn 2007-10-03 05:07:12 PDT 
(In reply to comment #3)
> Please read the version numbers you are reporting closely.  Safari 3.3 does not
> exist, so I assume you are referring to Safari 3.0.3.
> What URL can be used to reproduce this issue?

(In reply to comment #3)
> Please read the version numbers you are reporting closely.  Safari 3.3 does not
> exist, so I assume you are referring to Safari 3.0.3.
> What URL can be used to reproduce this issue?

I do not have an URL to show. The reason for not giving an URL is that we use
the page in our company and it uses private data of our customers. It access
the database in different ways.
Comment 5 Mark Rowe (bdash) 2007-10-03 19:43:38 PDT 
In that case you should create a standalone test case and attach it to the bug report.  We can't fix what we can't test.