Chrome 39 renders a compiled Dart app as blank - google-chrome

I am using Dart 1.8.3, Windows 8.1, Chrome 39.0.2171.95 m
Build a sample Polymer app from File > New Project dialog and chose polymerapp. It works fine in Dartium.
Compile to JS. Works fine in Firefox, but only shows a blank page in Chrome:
Searched here for some relevant topics and still getting nowhere. Would appreciate hints and guidance.

I guess this is because you need to start Chrome with --allow-file-access-from-files in order to be able or load local files.
Alternatively try to load the page from pub serve which does Dart2JS compilation on the fly (launch the page from DartEditor and then copy the URL from Dartium to Chrome).
Use any web server Python simplehttpserver or create on in Dart with a few lines of code.

I did the following test: deploy the build directory into my web server and it works fine. Thanks for the hint from Zochbauer that leads me to this.
In my view, this problem is more or less solved.

Related

CKEdit 4.13.1 fresh install won't run sample code properly on Chrome

Firefox runs the sample OK. No errors.
With the Chrome Browser the sample page comes up but the editor box is missing. Chrome says:
Uncaught TypeError: Cannot read property 'options' of undefined
at new $ (ckeditor.js:797)
at Object.beforeInit (ckeditor.js:800)
at Object.<anonymous> (ckeditor.js:286)
at e (ckeditor.js:265)
at Object.load (ckeditor.js:265)
at ckeditor.js:286
at CKEDITOR.resourceManager.<anonymous> (ckeditor.js:272)
at CKEDITOR.resourceManager.<anonymous> (ckeditor.js:270)
at e (ckeditor.js:265)
at Object.load (ckeditor.js:265)
What should I do? -- btw the OS is Xubuntu 18.04
I found the problem. I had downloaded the basic editor first and decided I wanted more features so I deleted everything and then downloaded a more feature rich package.
Chrome was caching some of the code and apparently the two versions are not compatible.
When I moved the sample code to a new directory on the server it functioned fine. I just can't make Chrome dump it's cache and reload all assets. CTRL + Refresh doesn't do it.

chrome extension reload on file change

I've been searching for-ever!
I`m working on windows and ubuntu, mostly on windows.
I searched the web for lot's of external libraries such as opn, open etc' but none of these could open this URL:
chrome://extensions
I want to put in the the script tag inside package.json
or in my build.js script
so that every time after I run "npm run build"
the chrome://extensions page will reload and also the additional page I`m testing on.
I once was able to do that exactly, but I lost that solution.
part of the problem is that I can't open chrome:
the ':' symbol is not recognized in the OS as valid protocol or something and it is escaped from chrome address bar if executed from command line.
I have tried many solutions.
I am not happy with the different resolutions proposed in the research I've made in Stack.O.
reloader as an extension is out of the question I want a script.
your kind help.
Assaf.
Clerc - for Chrome Live Extension Reloading Client
I built Clerc for exactly this purpose. npm run build won't be enough though. You need to hook up a LiveReload compatible server to watch for file changes, and clerc will listen for the reload messages.
Edit: Oh sorry. I missed the part where you said "reloader is out of the question". I still think this is your best option though.

"window.openDatabase is not a function" error in chrome app

When i run my index.html from chrome browser everything works fine but after i created a chrome app from the same files and tried to run the app i get "window.openDatabase is not a function" error.Did i miss something? I've heard that WEBsql is being depreciated but if that's the problem then why is it working on my browser?The only change i made to the folder with my html/js/css files in order to create the chrome app was adding a manifest and a background.js,i also changed window.localstorage with chrome.storage.local
Chrome has refused to support it in apps.
Given that WebSQL is deprecated, it's extremely unlikely that we'd expose the API in new contexts.
It has been noted that you can workaround by using it inside a webview. Here is the relevant issue.

Google Chrome extension development environment

As the title suggests I'm looking for a better Chrome extension development environment. I'm using Sublime Text 2 for my IDE, which is fine. The problem lies with testing the extension. Right now, when I need to test the code I've written I first have to launch Chrome with the –enable-easy-off-store-extension-install parameter. Then I need to package it through Chrome as an .crx file. Finally I have to drag and drop the file into Chrome and manually install it. Obviously this can get very time consuming very quickly.
I know I can test an extension as an unpacked extension, but this causes permission errors which is a problem since I need to perform CORs. Is there a better way to test extensions in Chrome?

FileReader API working in jsFiddle, but not from local file

I'm working on a Chrome/Firefox extension which will be using the file API to store files locally. I'm trying to get an example up and running but I'm running into issues which seem to center around Chrome. Can anyone explain why this jsFiddle works fine, but the exact same code, when run from a local file, doesn't work. Please note that it works fine in Firefox, just not in Chrome. Any ideas?
Chrome has unusually restrictive web security; many things, like Ajax, won't work when run locally. This is one of them. You can get around this problem by either using a local websever, like #ephemient suggests, or you can run Chrome in unsafe mode for testing:
chrome.exe --disable-web-security
Yep. Chrome's SOP prevents just about everything in file:// from working[1]. Use a local webserver instead.
If you are using chrome. Start the chrome from command line with the flag
--allow-file-access-from-files
chrome doesn't support for accessing local file without this flag.