Safari is actualy a very good standards compliant browser. However like many browsers how it handles events is often slightly different between browsers. I would think that it is an issue with the browser engine in safari and how it handles the code Courselab produces.
Exploder is courselabs main target, mainly as it still represents the main browser in web use with about 50% of the market. In most commercial and institutional settings exploder does represent closer to 100%.
It is really difficult to make a complex script or wen delivered content work in the same way on all browser engines, you'd need a huge number of work arounds for different versions of the main browser engines and for the different generations of each of them.
This isn't helpful I know but it does explain the why it's not working.
It is possible that sequencing the page events differently might help, maybe having the sound in a timeline as a sequential action might work. It all depends on how the safari engine interprets the code.
Safari is actualy a very good standards compliant browser. However like many browsers how it handles events is often slightly different between browsers. I would think that it is an issue with the browser engine in safari and how it handles the code Courselab produces.
Exploder is courselabs main target, mainly as it still represents the main browser in web use with about 50% of the market. In most commercial and institutional settings exploder does represent closer to 100%.
It is really difficult to make a complex script or wen delivered content work in the same way on all browser engines, you'd need a huge number of work arounds for different versions of the main browser engines and for the different generations of each of them.
This isn't helpful I know but it does explain the why it's not working.
It is possible that sequencing the page events differently might help, maybe having the sound in a timeline as a sequential action might work. It all depends on how the safari engine interprets the code.
