Skip to content

Conversation

DanielRuf
Copy link
Contributor

Description

This Pr fixes the regression caused by using stop() instead of finish().

Types of changes

  • Documentation
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (anything that would change an existing functionality)
  • Maintenance (refactor, code cleaning, development tools...)

Checklist

  • I have read and follow the CONTRIBUTING.md document.
  • The pull request title and template are correctly filled.
  • The pull request targets the right branch (develop or develop-v...).
  • My commits are correctly titled and contain all relevant information.
  • I have updated the documentation accordingly to my changes (if relevant).
  • I have added tests to cover my changes (if relevant).

@sonarqubecloud
Copy link

sonarqubecloud bot commented Apr 8, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@DanielRuf DanielRuf requested a review from joeworkman April 8, 2020 16:02
@DanielRuf
Copy link
Contributor Author

@joeworkman we need a new release then as this fixes some issues caused by the last release.

@joeworkman
Copy link
Member

Sure. do we need any others besides this one?

@DanielRuf
Copy link
Contributor Author

Probably just this one here. Not sure about the download link #12042 as the current zip download link throws an error.

Copy link
Member

@joeworkman joeworkman left a comment

Choose a reason for hiding this comment

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

I was not aware of .finish(). that is definitely better.

@joeworkman
Copy link
Member

Do we want to get the browserstack build working?

@DanielRuf
Copy link
Contributor Author

Do we want to get the browserstack build working?

It works / runs after the merge ;-)
GitHub does not share the secrets with forks which is ok that it fails here. This is why we also should have master and develop for releases. So it will run on develop after this. And when you do a new release it should be fine then.

@joeworkman
Copy link
Member

OK. So we want to release 6.6.3 with just this and the download fix?

@DanielRuf
Copy link
Contributor Author

Exactly.

@joeworkman joeworkman merged commit 33d9579 into foundation:develop Apr 8, 2020
@DanielRuf DanielRuf deleted the fix/12044-accordion-finish-running-animations branch April 8, 2020 18:12
@joeworkman
Copy link
Member

This pull request has been mentioned on Foundation Open Source Community. There might be relevant details there:

https://foundation.discourse.group/t/foundation-v6-6-3-released/2095/1

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

Successfully merging this pull request may close these issues.

[Bug][6.6.2] Accordion height for pre "is-active" accordion item not correct
2 participants