You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 24, 2019. It is now read-only.
Copy file name to clipboardExpand all lines: modules/scroll/README.md
+7-11Lines changed: 7 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -176,17 +176,13 @@ it to you to do it properly - whatever properly means in your book.
176
176
177
177
See [index.html](http://rawgithub.com/Hill30/NGScroller/master/src/index.html)
178
178
179
-
###Debugging coffeeScript directly in the browser
180
-
181
-
With adding sourceURL setting the source maps for the coffeScript seem to be functional now - at least with Chrome. You can set breakpoints and inspect values form the coffeeScript source window.
182
-
183
-
There is one dirty trick though - to make the breakpoints stick, the first one to be hit **has** to be set from the javascript source window. With the way the sample source code is, open the source code dropdown and select the source called 'src/scripts/application.js' under 'no domain', and place the breakpoint on the second line of the code in this file. Because of source mapping the blue arrow indicating the breakpoint will be put in the corresponding place of the coffeeScript code (application.coffee in this case), so you will not see it in the application.js. Now, if you refresh the page, Chrome will break on the first line of the code in the application.coffee.
184
-
185
-
Once the first breakpoint set up this way is hit, the rest of them will work just fine. You can set and/or remove them directly in coffeeScript. Just do not remove the first one - as soon as you do, the rest of you breakpoints while still visible in the editor will cease to work.
179
+
###History
186
180
187
-
Do not ask me why this woodoo is necessary, but as of Chrome version 30 it is just the way it is.
181
+
####v1.1.2
182
+
* Fixed inserting elements via applyUpdates error.
188
183
189
-
###History
184
+
####v1.1.1
185
+
* Fixed jqlite on $destroy error.
190
186
191
187
####v1.1.0
192
188
* Introduced API to dynamically update scroller content.
@@ -201,7 +197,7 @@ Do not ask me why this woodoo is necessary, but as of Chrome version 30 it is ju
201
197
* Registration of ui-scroll in bower.
202
198
203
199
####v1.0.1
204
-
* Deep datasource access via dot-notation in template.
200
+
* Deep datasource access via dot-notation in template.
205
201
*[Angular 1.3.x breaking change](https://github.com/angular/angular.js/issues/8876) fix with backward compatibility.
206
202
207
203
####v1.0.0
@@ -220,4 +216,4 @@ Introduced `is-loading` and `top-visible-*` attributes. Streamlined and added a
220
216
221
217
####v0.0.*
222
218
223
-
Initial commit including uiScroll, uiScrollViewPort directives and usage examples.
219
+
Initial commit including uiScroll, uiScrollViewPort directives and usage examples.
0 commit comments