It was a long time ago so i might be misremembering, but i think the idea was that safari would leak the target of redirects cross domain, which allowed the attacker to capture some of the oauth tokens.
So safari was not following the web browser specs in a way that compromised oauth in a common mode of implementation.
So safari was not following the web browser specs in a way that compromised oauth in a common mode of implementation.