Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon13.gif   ELOG on Chrome on MacOS?, posted by John Haggerty on Thu Dec 19 19:42:48 2013 
    icon2.gif   Re: ELOG on Chrome on MacOS?, posted by Stefan Ritt on Fri Dec 20 09:25:08 2013 
       icon2.gif   Re: ELOG on Chrome on MacOS?, posted by John Haggerty on Fri Dec 20 13:38:09 2013 
Message ID: 67640     Entry time: Thu Dec 19 19:42:48 2013     Reply to this: 67641
Icon: Disagree  Author: John Haggerty  Author Email: haggerty@bnl.gov 
Category: Bug report  OS: Mac OSX  ELOG Version: 2.9.2-2475 
Subject: ELOG on Chrome on MacOS? 
In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text.  I ran elogd -v by hand, 
and there were no obvious problems, and I looked at the developer consoles in Chrome, and the only place I see any hint of what the problem might 
be is the Javascript console which says this:

event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
Uncaught SecurityError: Blocked a frame with origin "http://localhost:8080" from accessing a frame with origin "chrome-
extension://pioclpoplcdbaefihamjohnefbikjilc".  The frame requesting access has a protocol of "http", the frame being accessed has a protocol of 
"chrome-extension". Protocols must match.
 fckeditorcode_gecko.js:36

It works ok in Safari, but it would be nice to use Chrome, and it was working ok until recently.  I don't think the problem occurred when I updated to 
Mac OS 10.9.1, but I don't keep careful track of the Chrome version.  It's not critical, but I pretty much exhausted what I knew how to debug.  I have 
close to the latest elog (2.9.2-2455), although I see the same phenomenon on this elog (.2.9.2-2475) and I think it's related to this thread:

http://productforums.google.com/forum/#!msg/maps/hQhwWA56NbA/2XL35dU7le4J

I tried the prescription in the October 22 entry, but it didn't seem to help, although I wasn't sure I had really tested it with compressed javascript and 
cache and what have you.
ELOG V3.1.5-fe60aaf