Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 339454

Summary:	Using "back" in chrome from editor to navigator can cause OAHub to write console errors
Product:	[ECD] Orion	Reporter:	Simon Kaegi <simon_kaegi>
Component:	Client	Assignee:	Project Inbox <e4.orion-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	0.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Simon Kaegi

2011-03-09 21:11:09 EST

Using "back" in chrome from the editor to the navigator can cause problems. When you go "back" as opposed to navigating it appears you have part of the old DOM still intact and this is causing errors in OAHub to be logged as the old plugin IFrames try to talk to a newly instantiated plug registry and OAHub thinks a phishing attack is occuring. Apart from the errors in the console this does not seem to break stuff but we should probably look to understand better what it going on here soon after the milestone.

Comment 1 Simon Kaegi

2011-06-15 11:16:26 EDT

We're using postMessage directly so this is no longer an issue.