navigation.js.coffee in upjs-rails-0.17.0

- old
+ new

@@ -117,18 +117,18 @@
       <a href="/foo" up-follow>Foo</a>
 
   The user clicks on the link. While the request is loading,
   the link has the `up-active` class:
 
-      <a href="/foo" up-follow up-active>Foo</a>
+      <a href="/foo" up-follow class="up-active">Foo</a>
 
   Once the link destination has loaded and rendered, the `up-active` class
   is removed and the [`up-current`](/up-current) class is added:
 
-      <a href="/foo" up-follow up-current>Foo</a>
+      <a href="/foo" up-follow class="up-current">Foo</a>
 
-  @selector [up-active]
+  @selector .up-active
   @stable
   ###
   sectionClicked = ($section) ->
     unmarkActive()
     $section = enlargeClickArea($section)
@@ -160,11 +160,11 @@
       </nav>
 
   If the browser location changes to `/foo`, the markup changes to this:
 
       <nav>
-        <a href="/foo" up-current>Foo</a>
+        <a href="/foo" class="up-current">Foo</a>
         <a href="/bar">Bar</a>
       </nav>
 
   \#\#\#\# What's considered to be "current"?
 
@@ -187,10 +187,10 @@
 
   For instance, the following link is highlighted for both `/reports` and `/reports/123`:
 
       <a href="/reports" up-alias="/reports/*">Reports</a>
 
-  @selector [up-current]
+  @selector .up-current
   @stable
   ###
   up.on 'up:fragment:inserted', ->
     # If a new fragment is inserted, it's likely to be the result
     # of the active action. So we can remove the active marker.