Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339454 - Using "back" in chrome from editor to navigator can cause OAHub to write console errors
Summary: Using "back" in chrome from editor to navigator can cause OAHub to write cons...
Status: RESOLVED WORKSFORME
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-09 21:11 EST by Simon Kaegi CLA
Modified: 2011-08-30 10:22 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Kaegi CLA 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 CLA 2011-06-15 11:16:26 EDT
We're using postMessage directly so this is no longer an issue.