[oslc-core] Problem in Delegated UI Window Name protocol example

[Steve K Speicher]

I believe there was some goal to keep the samples "clean" by just using
standard HTML/JS/DOM and not put browser-specific checks in (hard to draw
the line where to stop with this).

I'm fine either way though, as the reality is people will snag these and
want to use them.  Perhaps it would be good to attach a more complete
example to the spec (provide a reference to) or handle this with other
supporting material, which we tried to do with IBM Developer Works
articles, etc.

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645

> From: Dave <snoopdave at gmail.com>
> To: oslc-core <oslc-core at open-services.net>
> Date: 02/17/2011 10:03 AM
> Subject: [oslc-core] Problem in Delegated UI Window Name protocol
example
> Sent by: oslc-core-bounces at open-services.net
>
> Jazz developer Matt Jarvis just pointed out that our Delegated UI
> example for Window Name Protocol does not work properly on IE.
> Apparently, setting frame.onload = function() only results in an event
> on Firefox. For IE, we may need to use the IE-specific
> iframe.attachEvent instead.
>
> I propose that we modify the example so that it checks for IE and does
> the right thing.
>
> Any objections to that?
>
> Thanks,
> - Dave
>
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net


_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20110217/558e6d70/attachment-0003.html>