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
Copy file name to clipboardExpand all lines: README.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,14 +54,21 @@ e.g if a new component has been added in run time we need to update our library
54
54
55
55
status could be update ,destroy and refresh depending upon the change in navigation required in application.
56
56
57
-
-There is one more API for getting the current focused element by navigation. "By navigation" explicitly means that if focus is been hindered by other thing we might lose track of the desired navigation.
57
+
-There is one more API for getting the current focused element by navigation. "By navigation" explicitly means that if focus is been hindered by other thing we might lose track of the desired navigation.
58
58
59
59
Current active element can be used to attach events. Like one can attach `click` event on element and can use `ng-click` on top of that.
60
60
61
61
```javascript
62
62
naviBoard.getCurrentActiveElement()
63
63
```
64
64
65
+
- You can attach event according to component currently having the access for navigation by getting the current rendered component and can map it to different event.
66
+
67
+
68
+
```javascript
69
+
naviBoard.getCurrentComponentRendered()
70
+
```
71
+
65
72
Happy Coding!!!
66
73
67
74
> Use **naviboard** and suggest changes or modification required as its a small step for *developers* to save their time in order to navigate in feature phone applications instead writing lot of extra lines.
0 commit comments