Below is a list of Silverlight 3 Beta bugs you might run into. The plan is for at least most of these to be fixed at some point in the future.
Note: there are only a few bugs listed at the moment. I’ll probably post more later.
Removing an Offline Application on a Mac might leave the install in a bad state.
Users can run into this bug by doing the following:
1. User installs an offline application on a Mac.
2. User attempts to uninstall the offline application by right clicking over offline app and choosing “Remove this application”
3. Dialog comes up from Silverlight saying “Are you sure you want to remove the applcation?” and user clicks “Yes”.
4. Dialog comes up from operating system to authenticate Admin user name and password and user clicks “Cancel”.
At this point, the offline application is in a state where it is difficult to re-install or fully uninstall the offline application.
Computers with chips using SSE1 instructions sets will crash if the Silverlight application is using Pixel Shaders
For Silverlight 3 Beta, Pixel Shaders in Silverlight applications will crash computers that use old processors with SSE1instructions sets. When this bug is fixed, pixel shaders will simply not render for SSE1.
Cross-domain web-services that don’t have a clientaccesspolicy.xml and have a long 404 error response may stop working in SL3 Beta.
The scenario is this:
– Silverlight site does a cross-domain network access (which requests clientaccesspolicy.xml from the server)
– Server does not have a clientaccesspolicy.xml and thus issues a 404 error
– the error page, however, is customized in a way that the response is much larger than the default 404 error page
– due to this long response, we now go down the wrong code path in SL3 and don’t request crossdomain.xml
– in Silverlight 2 we do the normal fallback, which is requesting the crossdomain.xml
Net, net, cross-domain web-services that don’t have a clientaccesspolicy.xml and have a long 404 error response may stop working in SL3 Beta.