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

Themable Dialog animations #604

Merged
merged 2 commits into from Oct 15, 2018
Merged

Conversation

bryanforbes
Copy link
Member

Type: bug / feature

The following has been addressed in the PR:

  • There is a related issue
  • All code matches the style guide
  • Unit or Functional tests are included in the PR

Description:

Allows customization of animations via CSS

Resolves #578

@codecov
Copy link

codecov bot commented Oct 5, 2018

Codecov Report

Merging #604 into master will increase coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #604      +/-   ##
==========================================
+ Coverage   98.94%   98.94%   +<.01%     
==========================================
  Files          42       42              
  Lines        3043     3044       +1     
  Branches      820      822       +2     
==========================================
+ Hits         3011     3012       +1     
  Misses         32       32
Impacted Files Coverage Δ
src/dialog/index.ts 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4511d72...a50b2a9. Read the comment docs.

@pottedmeat pottedmeat self-requested a review October 11, 2018 21:24
@@ -160,8 +159,8 @@ export class DialogBase<P extends DialogProperties = DialogProperties> extends T
const { underlay } = this.properties;
return v('div', {
classes: [ this.theme(underlay ? css.underlayVisible : null), fixedCss.underlay ],
enterAnimation: animations.fadeIn,
exitAnimation: animations.fadeOut,
enterAnimation: this.theme(css.underlayEnter) || undefined,
Copy link
Contributor

@smhigley smhigley Oct 15, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably update to SupportedClassName typings in framework/widget-core so this isn't necessary 😝

@@ -172,8 +171,8 @@ export class DialogBase<P extends DialogProperties = DialogProperties> extends T
aria = {},
closeable = true,
closeText,
enterAnimation = animations.fadeIn,
exitAnimation = animations.fadeOut,
enterAnimation = this.theme(css.enter) || undefined,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another thought -- would it make sense to add enterAnimationActive and exitAnimationActive properties to support both transitions and animations for increased styling flexibility? Using keyframes for a simple opacity fade in/out seems overkill, although I suppose any given transition could be made into an animation. Your call.

@agubler agubler merged commit c9f4cf7 into dojo:master Oct 15, 2018
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

4 participants