You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although text/javascript is the current best practice per discussion in #568 and noted in the HTML standard, the practical value of switching from application/javascript to text/javascript is relatively low.
More importantly this recommendation continues to cause confusion within the community as application/javascript was previously recommended by the IETF which hasn't yet updated RFC 4329 to recommend text/javascript (though an active draft exists which will make that change).
Given the conflicting state of currently published standards, the level of confusion this causes, and the limited practical benefit of using one of these mime types over the other, I propose changing hint-content-type to not raise any issues when application/javascript is used.
Note the recommended type would remain text/javascript with this change and warnings would still occur with this recommendation when any other mime-type is used (e.g. application/x-javascript).
Also note that users would still be able to override the new behavior in .hintrc to require a single type of their choosing if desired.
The text was updated successfully, but these errors were encountered:
antross
changed the title
Suppress warnings when application/javascript is used by default
Suppress warnings when application/javascript is used
Jun 19, 2019
antross
changed the title
Suppress warnings when application/javascript is used
Suppress warnings when application/javascript is used [0.2]
Jul 5, 2019
gesa
pushed a commit
to gesa/hint
that referenced
this issue
Jul 19, 2019
Although
text/javascript
is the current best practice per discussion in #568 and noted in the HTML standard, the practical value of switching fromapplication/javascript
totext/javascript
is relatively low.More importantly this recommendation continues to cause confusion within the community as
application/javascript
was previously recommended by the IETF which hasn't yet updated RFC 4329 to recommendtext/javascript
(though an active draft exists which will make that change).Given the conflicting state of currently published standards, the level of confusion this causes, and the limited practical benefit of using one of these mime types over the other, I propose changing
hint-content-type
to not raise any issues whenapplication/javascript
is used.Note the recommended type would remain
text/javascript
with this change and warnings would still occur with this recommendation when any other mime-type is used (e.g.application/x-javascript
).Also note that users would still be able to override the new behavior in
.hintrc
to require a single type of their choosing if desired.The text was updated successfully, but these errors were encountered: