Bug 39186

Summary:

Google Wave broken, reports an error while loading

Product:

WebKit

Reporter:

Ain Tohvri <ain>

Component:

New Bugs

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED WORKSFORME

Severity:

Normal

CC:

Priority:

Version:

528+ (Nightly build)

Hardware:

Mac (Intel)

OS:

OS X 10.6

Attachments:

Description	Flags
Unsynced waves	none
Errors on Google Wave	none

Ain Tohvri

Reported 2010-05-16 14:13:28 PDT

Created attachment 56194 [details] Unsynced waves 1. Log in to Google Wave 2. While loading, error appears "Everything's shiny, Cap'n. Not to fret!" An error has occurred, please refresh." 3. Select a wave 4. "Unsynced waves" appears in Navigation tab The behaviour hasn't been there before, looks like a similar issue to bug 39023. Error from the console: "No relay set (used as window.postMessage targetOrigin), cannot send cross-domain message" at core:rpc:490

Attachments
Unsynced waves (18.04 KB, image/png) 2010-05-16 14:13 PDT, Ain Tohvri	no flags	Details
Errors on Google Wave (24.35 KB, image/png) 2010-05-16 14:16 PDT, Ain Tohvri	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Ain Tohvri

Comment 1 2010-05-16 14:16:38 PDT

Created attachment 56195 [details] Errors on Google Wave

Alexey Proskuryakov

Comment 2 2010-05-17 15:52:09 PDT

We can't reproduce this so far. Can you try to find out which nightly build this started with for you?

Ain Tohvri

Comment 3 2010-05-18 03:18:58 PDT

Just checked it, I first encountered it on May 8th and since I'm always running the latest WebKit nightly, it must be the most recent one at that time. I hope you can check it up.

Ain Tohvri

Comment 4 2010-05-18 03:20:49 PDT

Correction: May 9th for Google Wave and May 8th for Google Analytics as described in bug 39023.

Alexey Proskuryakov

Comment 5 2010-05-24 08:31:14 PDT

Per a comment made in bug 39249, this is still reproducible for the reporter in r60027 nightly.

Ain Tohvri

Comment 6 2010-06-16 01:38:53 PDT

I can confirm this working on r61173 + Safari 5 after 10.6.4 update today. Looks like it has landed.

Note You need to log in before you can comment on or make changes to this bug.