Fix issue on demo page with dark reader #21
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #20 and https://discourse.elm-lang.org/t/runtime-errors-caused-by-chrome-extensions/4381?u=mweiss
The demo page uses font-awesome, which inserts a style element in the beginning of the body. However, dark reader, a chrome and firefox extension, will then insert its own style element after it for its own purposes and logic. This confuses Elm's virtual dom, which just crashes and doesn't recover. This is a workaround to wrap the styles in a div so even though its own of sync, because it never changes position in the app, it'll end up working.