I have enabled source maps and workspaces in Chrome Canary to be able to edit *.coffee files directly in the browser. Yet the default editor in Chrome does not have syntax highlighting for CoffeeScript files, at least I could not find it. Is there a way or extension to enable that?
This was recently implemented in https://codereview.chromium.org/18341003/
Related
I've taken a look at the documentation but it's a little thin on what values are acceptable. Does anyone know if there's a value to open Google Chrome incognito and/or have a complete list (who knows I might want to open a project in IE/Edge one day).
I've tried:
browser: "google chrome -incognito"
browser: "-incognito"
browser: "incognito"
Not many more alternatives, I reckon.
Thanks in advance!
Chrome's command line switch is actually --incognito (two dashes), but I tried it in my browsersync Gulp task and that didn't work.
The workaround I'm using is to use a Chrome extension to switch my development domain name to incognito. It looks like there are a couple extensions that do that, I use Ghost Incognito:
https://chrome.google.com/webstore/detail/ghost-incognito/gedeaafllmnkkgbinfnleblcglamgebg?hl=en-US
in general, I created a shortcut to launch the browser in private mode. then in browser-sync settings added parameter:
browser: 'absolute path to shortcut'
Hurrah!
I was trying to create a Chrome extension that hides all the existing extension icons (can't be disabled), is there any way to do it?
Extensions cannot change chrome's settings or appearance(with a few exeptions).
Extension apis like you are suggesting would be very invasive and most likely unwanted from most users.
I tried to enable support for sass source mapping in Chromium (v31.0.1606.0) but it seems that there is the "Support for SASS"-option missing in my case.
I followed those instructions:
http://fonicmonkey.net/2013/03/25/native-sass-scss-source-map-support-in-chrome-and-rails/
Screenshot of my "Experiments"-Window:
see http://i.stack.imgur.com/UhFNp.png
Hint: I also tried it with Google Chrome Canary and Chrome v30 and it didn´t worked either.
This one got me too, after reading a NetTuts article on Developing With Sass and Chrome DevTools. Seems like most articles on the subject are outdated.
Turns out Chrome v30 and later ship with souce maps and SASS support enabled by defualt. In v29 and earlier you have to check the "Support for SASS" box.
Furthermore, according to Google:
"Currently Sass is the only preprocessor that supports CSS source maps..."
So as long as you don't uncheck "Enable CSS Source Maps" in Dev Tools > Settings > General, you can hack away at your scss/sass directly from chrome.
I followed the Google Dev Tools docs and got it working on OSX.8 with Canary 32.0.1664.3. Here are the key points:
Make sure you're using sass 3.3.0alpha
gem install sass -v '>=3.3.0alpha' --pre
Add the --sourcemap flag when you run sass from shell
sass --watch --sourcemap sass/styles.scss:styles.css
Optionally enable "Auto-reload generated CSS" in Dev Tools > Settings > General for real-time goodness.
Here's a screenshot from my machine immediately after following the above steps and firing up a site with Sass.
Sources:
Working with CSS Preprocessors - Chrome DevTools – Google Developers
Developing With Sass and Chrome DevTools | Nettuts+
Our team uses Chrome Web Developer tools to debug JavaScript. As of yesterday when our browsers upgraded to Chrome Version 27.0.1453.93, the Sources section no longer lists all the JavaScript files. Does anyone know if this is a bug or if there is a setting? Some JavaScript files are still listed but I can't find the criteria for files being listed or not. I checked on an older Chrome Browser pointing to the same URL and all the files are listed. Anyone solved this?
I guess you may have some javascript code that has been loaded dynamically. If it is the case, you should use the phrase
//# sourceURL=foo.js
at the beginning of your javascript code. foo.js will be assigned it by debugger. And debugger will show it with that name.
chrome and firebug accept it, I am not sure about other browsers
I'm trying to use the Chrome Experimental Devtools API.
I've tried running Chrome with: --enable-experimental-extension-apis as suggested here: http://developer.chrome.com/extensions/experimental.html and enabled the "Experimental Extension APIs" in the flags settings.
When I open the Console in Chrome (or Canary), I get the following:
chrome.devtools: undefined
chrome.experimental: undefined
I'm running Chrome 21.0.1180.77 beta-m. I've also tried Canary.
What am I missing?
As explained here: http://developer.chrome.com/extensions/devtools.html, the chrome.devtools APIs are only available in your devtools HTML page.
First, you need to create an HTML file and then add it to your extension's manifest under the "devtools_page" key. When you load your extension into Chrome and open the DevTools, you should see your new tab.
In that tab is the only place chrome.devtools will work.
chrome.experimental is different and will be available in all of your background pages and content scripts.
You need to run it only in Canary.
Plus when you run chrome add this flag to the command line:
path_to_chrome.exe --enable-experimental-extension-apis