safari: fix createOffer callbacks API #860
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change fixes a bug where the legacy callbacks API for Safari
createOffer didn't return as expected when compared to the currently
working promises API.
This was due to the order of shims in adapter_factory, where the
shimCreateOfferLegacy which does trasceiver stuff and overwrites the
createOffer prototype was called after shimCallbacksAPI already fixed
the createOffer function to support callbacks.
Moreover, this happened only because the order of arguments to
createOffer int he first place, where the callbacks come first (wtf)
before the options, meaning that the options argument changes order
between the callback and promise API. If only we could go back in
time...
Fixes #859
Description
Purpose