Skip to content

broken links fix #365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 22, 2019
Merged

broken links fix #365

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion app/ng-ui-widgets-category/tab-view/basics/article.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,4 +5,4 @@ HTML

* tabItem: This directive uses a JSON object to transfer properties to the native object. Actually, `TabViewItem` is a pretty simple object with just `title`, `iconSource` and `view` properties. Since `title` and `iconSource` are usually represented as text, TabView directive uses a small JSON object (`{title: 'Profile', iconSource: '~/icon.png'}`) to define these properties easily in HTML. The view however, is not so simple, therefore the directive uses the tag where `tabItem` attribute is set as view. Currently, the directive also holds the property `textTransform` which controls the capitalization of the tab title text. See the Styling section for more information.

> Note: If you have set the `iconSource` property on a `TabViewItem`, but are not seeing any icons next to the title, this might be because the icon is not present in your App_Resources folder. See the [Working with Images]({%slug images#load-images-from-a-resource %}) article for information on how to add and reference your resource images.
> Note: If you have set the `iconSource` property on a `TabViewItem`, but are not seeing any icons next to the title, this might be because the icon is not present in your App_Resources folder. See the [Working with Images]({%slug images%}#load-images-from-a-resource) article for information on how to add and reference your resource images.