Jason Buckner
Jason Buckner
I was trying to do this today and came across [this comment](https://github.com/ebryn/ember-component-css/issues/8#issuecomment-78074243) that said it should already be supported, but it's not working for me either.
Yeah I figured this would be tricky data-wise while still being (mostly) client-side, I just wanted to start the conversation to see if some creative solutions like yours came up...
What about building an option to export the derive configuration and tracks as a JSON file. The user could upload that file to a server configured with the proper CORS...
This update seems to have some issues running tests, closing for now.
Actually, I was wrong, the tests pass. The issue was related to me switching between node versions while testing.
Hmm I didn't account for when there are multiple router-slots on screen. With this PR, it would put multiple click listeners on the window and only respond to the router...
That was an easy fix. Now I'm only binding the anchor handler in the root router so we only get one click handler and since it's being used to determine...
I was interested in a similar use case and opened https://github.com/andreasbm/router-slot/pull/18 which I think will do what you're looking for. It skips any anchor links not handled by the router...
Thanks for posting this. I renamed my `master` branch to `main` and re-cloned my repo and thought something broke. I'm seeing the same that @jamesboehmer posted. I renamed `main` back...
Seeing this as well and it causes several styles to break when the DOM is flattened.