Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Safari 9.1.1. Issue - "A problem repeatedly occurred" #309

Closed
pburtchaell opened this issue Apr 27, 2016 · 4 comments
Closed

Safari 9.1.1. Issue - "A problem repeatedly occurred" #309

pburtchaell opened this issue Apr 27, 2016 · 4 comments

Comments

@pburtchaell
Copy link

pburtchaell commented Apr 27, 2016

Earlier this month I noticed an issue with some websites I built HTML for using this plugin: when landed in Safari, the page is reloaded several times and finally, shows "A problem repeatedly occurred."

screen shot 2016-04-27 at 10 32 14 am

Initially, I thought it was an issue with permissions from AWS S3 or an issue with my code. However, after digging a bit further, I discovered something rather alarming: if you use <script src="/app.js"></script> the page reloads. If you use <script type="text/javascript" src="/app.js"></script>, the page loads as expected. Considering it is a part of the HTML5 standard to exclude the type attribute, I am wondering... is this actually a Safari bug or am I missing something here? Is anyone else having this issue?

Note, this also occurs when I do not use this plugin (such as when I am using local development server). However, considering the script tag is central to this plugin, I figured I'd make an issue here to see if anyone else encountered this.

Edit, some examples of websites:

@jantimon
Copy link
Owner

You are right - this has to be fixed.
If you have time to fix it please update it here: https://github.com/ampedandwired/html-webpack-plugin/blob/master/index.js#L441

Otherwise I will do it myself in the next days.

@pburtchaell
Copy link
Author

PR opened in #311.

@jantimon
Copy link
Owner

jantimon commented May 5, 2016

Closed because of #311

@lock
Copy link

lock bot commented May 31, 2018

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants