Re: [cesium-dev] Cesium 1.7 Infobox error

[Matthew Amato]

This was an issue that slipped out with 1.7, we have already release 1.7.1 to fix it: http://cesiumjs.org/2015/03/02/Cesium-version-1.7.1-released/

On Mon, Mar 9, 2015 at 6:21 PM, Katone Vi <tonym...@gmail.com> wrote:

Hello Cesium,

After updating the project to Cesium 1.7, I began getting errors upon clicking czmlDataSources (which should pop up the InfoBox widget)

TypeError: Cannot read property 'background-color' of null

    at null.wa (http://localhost:8080/cesium-cop/Source/Widgets/InfoBox/InfoBox.js:123:63)

    at Function.A.notifySubscribers (http://localhost:8080/cesium-cop/Source/ThirdParty/knockout-3.2.0.js:33:55)

    at Function.d.W (http://localhost:8080/cesium-cop/Source/ThirdParty/knockout-3.2.0.js:36:179)

    at d [as _descriptionSanitizedHtml] (http://localhost:8080/cesium-cop/Source/ThirdParty/knockout-3.2.0.js:36:71)

    at knockout.defineProperty.set (http://localhost:8080/cesium-cop/Source/Widgets/InfoBox/InfoBoxViewModel.js:100:56)

    at f [as description] (http://localhost:8080/cesium-cop/Source/ThirdParty/knockout-3.2.0.js:43:512)

    at Viewer._onTick (http://localhost:8080/cesium-cop/Source/Widgets/Viewer/Viewer.js:1325:46)

    at Event.raiseEvent (http://localhost:8080/cesium-cop/Source/Core/Event.js:146:30)

    at Clock.tick (http://localhost:8080/cesium-cop/Source/Core/Clock.js:203:21)

    at CesiumWidget.render (http://localhost:8080/cesium-cop/Source/Widgets/CesiumWidget/CesiumWidget.js:633:39)

I tried looking into this by checking out infobox.js

                if (frameContent.childNodes.length === 1) {

                    var style = window.getComputedStyle(frameContent.firstChild);

                    var color = Color.fromCssColorString(style['background-color']);

                    if (color.alpha !== 0) {

                        infoElement.style['background-color'] = style['background-color'];

                    }

                } else {

                    infoElement.style['background-color'] = null;

                }

And the problem occurs when frameContent.childNodes.length === 1... which is whenever i click my czmlDataSource.  Any ideas?  Thanks!

Katone

--
You received this message because you are subscribed to the Google Groups "cesium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cesium-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris]

Hi Matt,

On the topic of InfoBox in Cesium 1.7.1, Chrome 41.0 (Ubuntu) throws a sandbox error on about:blank.  

"Blocked script execution in 'about:blank' because the document's frame is sandboxed and the 'allow-scripts' permission is not set."

This started happening after upgrading to Cesium 1.7.1 and after reading about the updates to InfoBox, I presume the issue is related.

I am serving Cesium from an HTTPS site with a self-signed cert.

It's not an issue but wanted to make your team aware and see if there were any workarounds other than modifying about:flags?

Thanks.

- Chris

[Matthew Amato]

Thanks, I'll make a note for us to look into this.  Originally we weren't even loading about:blank, but the browsers all behave differently if you don't load some form of page.  I think the solution may be to create an empty document to use rather than relying on about:blank.

[Matthew Amato]

Chris, I looked into this and I can't personally reproduce the problem.  What do you see when you go to about:blank in that browser? (be sure to view the source)  On my machine it is completely empty.  It's possible that you have some content scripts being injected into about:blank by various Chrome plug-ins and that's what's being detected by the iframe sandbox and putting up the error.  It's a harmless error, but I want to understand if it's something we should be doing differently on our end.

[Alexander Entin]

Just FUI.

I see the same error message in Chrome on Windows. about:blank source is empty.

[Katone Vi]

Alexander

I'm using Chrome on Windows 7 at the moment and I do not see the following error you are referring to.  Are you sure it's Cesium or perhaps your Chrome is outdated?

Katone

[Matthew Amato]

Alex, is this with the server that ships with Cesium, or your own server?  Can you describe your server setup?  I've tried this both under http and https on Windows and UNIX and can't reproduce it.

If you go to chrome://extensions/, what do you have installed? 

--

[Alexander Entin]

server: nginx, default setup (almost)

extensions: Adblock, Postman

[Alexander Entin]

http://localhost

[Alexander Entin]

It's Adblock.

Even being disabled for the given site it still produces the error.

[Matthew Amato]

I was just about to reply with a similar thought.  It looks like they are intentionally injecting code into about:blank.  They even filed a Chrome bug/feature request for it.  There's basically nothing we can do about it on our end because they are injected code into all iFrames, even sandboxed ones.  I would argue this is a bug in adblock.

On Thu, Mar 26, 2015 at 3:53 PM, Alexander Entin <alexand...@gmail.com> wrote:

It's Adblock.

Even being disabled for the given site it still produces the error.

--

[Matthew Amato]

Just to close the loop on this, Adblock says this is a Chrome bug and they opened the following issue for it: https://code.google.com/p/chromium/issues/detail?id=472101