troxler

@andrewducker Why do you think this is related to au-revoir-utm? Try to open that website in a clean (i.e. no addons) Chrome profile and the same thing happens. That site...

There is a [very similiar issue](https://github.com/necolas/normalize.css/issues/856) that was closed by Normalize's author just yesterday. Unfortunately, he did not leave any comment at all. Not sure what to make of that....

For the record: I removed Marx from the list for now. https://github.com/troxler/awesome-css-frameworks/commit/910446bbebb303a448f13c29404fda0bbbd2ce12

The content model of the [`a` element specification](https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-a-element) defines that "there must be no [interactive content](https://html.spec.whatwg.org/multipage/dom.html#interactive-content-2) descendant". A `button`—among other elements—is interactive content.

Blocked by https://github.com/chr15m/DoodleCSS/issues/9

The blocking issue is still open. So I'm closing this for now, feel free to reopen.

Thanks for the PR. The original project indeed looks dead and should be removed. But I'd like to wait for a stable release of the fork before I have a...

Duplicate of https://github.com/Quicksaver/Tab-Groups/issues/541 (there is also a workaround)

That just slows down the progress but still completes without calling `finish()`. This is especially not ideal when your loading times in general are short but sometimes very long.

For the record: I switched to https://github.com/rstacruz/nprogress which has this feature and works flawlessly in my Vue.js project.