Skip to content
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.

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

feat(ui,docs): Add back animation duration prop for QCarousel #4876 #5375

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

sskwrl
Copy link
Contributor

@sskwrl sskwrl commented Oct 23, 2019

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Documentation
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • It's submitted to the dev branch and not the master branch
  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • It's been tested on a Cordova (iOS, Android) app
  • It's been tested on a Electron app
  • Any necessary documentation has been added or updated [in the docs]

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Add transition-duration property to all components that support transitions
(QCarousel, QStepper, QTabPanel) allowing nested transitions to be viewed.
Previously, when the first transition completed, subsequent animations were
skipped showing the final state immediately. The transition-duration property
defines an explicit time (in milliseconds) for the total animation. All
transitions in this time are animated as intended. Examples requiring/using
this commit have been included in the appropriate ui/dev pages.

Documentation includes api description of transition-duration property and
examples requiring/using the property on each of the transition supporting
components.

Other information:

…ramework#4876

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [x] Feature
- [x] Documentation
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x ] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch and _not_ the `master` branch
- [x] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix: #xxx[,#xxx]`, where "xxx" is the issue number)
- [ ] It's been tested on a Cordova (iOS, Android) app
- [ ] It's been tested on a Electron app
- [x] Any necessary documentation has been added or updated [in the docs]

If adding a **new feature**, the PR's description includes:
- [x] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Add transition-duration property to all components that support transitions
(QCarousel, QStepper, QTabPanel) allowing nested transitions to be viewed.
Previously, when the first transition completed, subsequent animations were
skipped showing the final state immediately.  The transition-duration property
defines an explicit time (in milliseconds) for the total animation.  All
transitions in this time are animated as intended.  Examples requiring/using
this commit have been included in the appropriate ui/dev pages.

Documentation includes api description of transition-duration property and
examples requiring/using the property on each of the transition supporting
components.

**Other information:**
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant