Question: I use this layout :

```
<?xml version="1.0" encoding="UTF-8"?>
<ScrollView xmlns:android="http://schemas.android.com/apk/res/android"
    android:id="@+id/scroller"
    android:layout_width="fill_parent"
    android:layout_height="fill_parent"
    android:fillViewport="true" 
    android:background="#00868B">

<RelativeLayout 
 android:layout_width="match_parent"
 android:layout_height="wrap_content"
 >

  <TextView android:layout_height="wrap_content"
        android:layout_width="fill_parent" 

        android:gravity="center"
        android:layout_alignParentTop="true" 
        />
  <EditText

    android:layout_width="match_parent"
    android:layout_height="wrap_content"

  />

   <TextView android:layout_height="wrap_content"
        android:layout_width="fill_parent" 
        android:gravity="center"
        android:layout_below="@+id/title" />

    <EditText
    android:layout_width="match_parent"
    android:layout_height="wrap_content"

  />

 <Button ..
    android:layout_width="match_parent"
    android:layout_height="50dp" 
    android:text="@string/getloc" 

    />

 <Button ..
    android:layout_width="match_parent"
    android:layout_height="50dp" 

     />

 <Button ..
    android:layout_width="match_parent"
  ..
    android:layout_alignParentBottom="true" 

    />

</RelativeLayout>

</ScrollView>

```

There is no scrollview.
I want when the user enters sth in second textview to "go down" because else the textview gets bigger but the first button is steady and blocks the view.

Answer: 
The problem is that Chrome developer tools recently changed what version of source maps it supports. The article you mention details how to set up an older style of CSS source maps. However, Chrome now supports [version 3 source maps](https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit#heading=h.75yo6yoyk7x5). The new source maps puts the mapping in a separate \*.css.map file instead of inline in the compiled CSS file. The benefits of the new format is that it is much smaller and does not break styles for older Internet Explorers. The [link](http://net.tutsplus.com/tutorials/html-css-techniques/developing-with-sass-and-chrome-devtools/) that @justin-smith provided should point you in the right direction. However, from my findings, even though the pre-released version 3.3 of the SASS gem knows how to generate the .map files, there still needs to be support from the sass-rails gem to correctly serve these files from the Rails asset pipeline. I created a [repo](https://github.com/gerryster/rails4-v3-sourcemaps) in order to figure out the current state of support for v3 sass source maps in Rails. There may be a way to short circuit the asset pipeline and have the sass gem precompile files and put them in a directory which comes early in the asset path. However, I have not figured out how to to this.
As @gerryster said, Chrome now supports `source maps proposal v 3`. I wrote blog post about [Debugging Rails 4 CoffeeScript and Sass source files in Google Chrome](http://blog.vhyza.eu/blog/2013/09/22/debugging-rails-4-coffeescript-and-sass-source-files-in-google-chrome/).