Chrome dev tools : how to filter css styles by file name

Sometimes you need to analyze the css styles coming from a specific file, and the chrome developer tools shows all the style from all the linked css files.

Here is an example from NYT website:

If you need to focus only on a specific CSS file type the name on the filter box in the right upper corner, i.e. “_story.scss” :

Now you can browse other pages in the same website and you will see only the styles coming from the _story.scss file.

It works also if you have multiple css files with the same name but with different query strings:

style.css?ver=1.0.1
style.css?ver=2.0.0

Write in the filter box “ver=2.0.0” and you will see only the styles from the 2.0.0 version.

You can also edit and save the css file using this guide.

Hope this helps!

How to investigate IOS Safari crashes using Chrome

I’ve worked some days on a web app application, completely written using  jQuery, jQuery Mobile and Kendo UI Library.

The application worked successfully on the Android devices but, on Iphone/Ipad crashed unexpectedly.

I’ve tried to investigate the crash logs on the device, with no fortune.

I’ve also connected the device to a mac and tried to debug the web application using the Web Inspector, following these steps http://moduscreate.com/enable-remote-web-inspector-in-ios-6/ , but , when Safari on IOS crashed, the Remote Web Inspector on my Mac was closed too, with no possibility to find what was the latest javascript instruction.

I’ve discovered on the web a great project that enables Chrome debug on Safari for IOS, here is the link:

https://github.com/google/ios-webkit-debug-proxy

You need to install :

• Xcode
• Brew http://mxcl.github.com/homebrew/
• Chrome for Mac

After the proxy installation you need to execute it on your mac using :

ios_webkit_debug_proxy

Start the IOS simulator using XCode:

Connect chrome on your Mac to the address…  http://localhost:9221

Choose the device:

Here we are: Chrome web tools debugging Safari!

Network Panel:

Console window:

If Safari crashes… you will be able to see the console message in the web tools window.. this should save a lot of time when you try to find the crash point.

Some tips:

• don’t use web apps inside iframes : Safari on IOS in really unstable



• if you need to use jQuery ready event…. wrap the code inside a function and add a timer and call it after 100-200 ms



• sometimes working on css style overflox-x overflow-y seems to crash Safari



• read the Apple guidelines for web apps:

Hope it helps!

Matteo