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 has been archived by the owner on Aug 9, 2024. It is now read-only.
The following WebForms examples showcasing UI are directly affected by this issue:
- Miscellaneous > UI > Button
- Miscellaneous > UI > Panel
- Miscellaneous > UI > Progress Bar
- Miscellaneous > UI > Tab Panel
- Miscellaneous > UI > Tip
- Miscellaneous > UI > Window
By choosing either Triton (default) or Aria, the components with different UI= are not shown most of the time (if not at all times).
This has been identified when fixing #1217 items 117 to 122. It is not a side effect of the commit, as other themes works, but it was only possible to identify the issue after these items were fixed.
The text was updated successfully, but these errors were encountered:
Components' UI="Primary|Success|Info|Danger|Warning" styles have been added for the Triton theme. Supported in all browsers except IE8 and IE9. It is already in the repo and will be released with 4.1.0.
As for Aria, UI is not going to be supported for this theme, since it is a very specific theme. The Aria theme ComboBox option has been excluded.
The online examples will start working with the 4.1.0 release.
DaniilVeriga
changed the title
Component's UI property is not supported by Aria and Triton themes
Component's UI property is not supported by Triton theme
May 9, 2016
The following WebForms examples showcasing UI are directly affected by this issue:
- Miscellaneous > UI > Button
- Miscellaneous > UI > Panel
- Miscellaneous > UI > Progress Bar
- Miscellaneous > UI > Tab Panel
- Miscellaneous > UI > Tip
- Miscellaneous > UI > Window
By choosing either Triton (default) or Aria, the components with different
UI=
are not shown most of the time (if not at all times).This has been identified when fixing #1217 items 117 to 122. It is not a side effect of the commit, as other themes works, but it was only possible to identify the issue after these items were fixed.
The text was updated successfully, but these errors were encountered: