Speaking of things that would be good to fix now, not years later, Chrome defaults to same-origin-domain checks unless you jump through some hoops, while Firefox and the spec default to same-origin checks. Chrome's behavior makes more things depend on document.domain. @mikewest
-
-
Another example: Chrome's implementation of https://w3c.github.io/webappsec-credential-management/#same-origin-with-its-ancestors … (which you wrote at least the spec for!) doesn't match the spec because of this issue...
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.