OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Ajax - event source


At the F2F, it was suggested that the callback function receive the 
source of the event so that the callback would know what caused the
submission.

In IE, "event" is a global object, and the consumer function can get 
event.srcElement and pass it to the callback.

But, in Firefox/mozilla browsers, event is not global, and to get the 
event, event handler function must explicitly have the event argument,
from which it can extract event.target.

To make this work across browsers, the consumer supplied function will 
have to include an event arg which may or may not make sense depending
on where the URL is used. For instance, what is the event source when a 
URL is used in an inline script? The document itself?

Two questions:

1. Do you see any implementation issues if we require that the consumer 
to (optionally?) pass on the event source to the callback?

2. Is there a need for the event source? Since the portlet knows the 
context in which the URL is being used, it can get the source from the
document.

Thanks for any comments.

Subbu

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]