Introduce an option to change tag to inject Browsersync snippets #34
Conversation
This file contains hidden or 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
1 participant
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.
This pull request introduces a new option.
It changes tags to inject Browsersync's snippets.
This is a workaround for #15 . (I could not solve the root cause of #15 )
Browsersync may not work if the same problem as issue #15 occurs. Because the snippet for Browsersync is injected into
</ body>. The #15 issue causes</ body>not to be rendered, which can cause Browsersync to fail.The option introduced by this pull request allows you to move the tag to be injected into the first half of the code.
This will avoid this problem. It is rendered reliably by being injected into the tag.
This option allows to use the Browsersync feature until #15 is resolved.
Alternatively, this option can provide a solution for themes without tags.
For example, it is recommended that the [Google HTML/CSS Style Guide] not use the optional
<body>tag. This plugin can not be used than it is.However, if this pull request makes other tags available, then the plug-in will be available.
Like this, it is a function that can be used not only for the #15 workaround but also for others.