Illuminating the web, one framework at a time... see how the web really works!
- (2016-04-22) Johan van de Merwe: It looks very promising, it's an alpha release. Too bad it doesn't recognize that my app is using ExtJS version 6.
- (2014-11-28, v:2.0.2013.8203) Conor Moran: Install Fails - Invalid Manifest
I noticed recently that my chrome illuminations extension no longer works - presumably my version of chrome ahs been updated. I attempted to reinstall the extension (Chrome Version 39.0.2171.71 m) - I get an error, the console indicates that the extension has an invalid manifest file.
- (2014-11-20, v:2.0.2013.8203) Ivan Jouikov: Latest Chrome update broke Illuminations on Windows
Verified this on multiple computers and also verified that this doesn't affect OSX. With Chrome 38.0.2125.122 recently rolling out, upon restarting the browser, the Illuminations plugin is no longer shown and is not in Extensions. Trying to add it again results in error "There was a problem adding the item to Chrome. Please refresh the page and try again." Please advise; this is awesome plugin and I paid for my FireBug version a long time ago and would be happy to pay for this Chrome version to be fixed on Windows, as we use it extensively. Thanks!
- (2014-06-11, v:2.0.2013.8203) Xander King: Facebook SDK warning
Afternoon - Chrome version looking very tidy, good work! One thing: My man is adding facebook login to our app (sins in past life etc.) and I receive this console warning on page refresh, which goes away when I disable Illuminations: Received message of type object from https://[my host name], expected a string More specifically, it generates between 2000 and 7000 copies of that warning!? Linux Mint 15 Chrome 35.0.1916.153