Confirmed users
239
edits
Security/Inline Scripts and Styles: Difference between revisions
Security/Inline Scripts and Styles (view source)
Revision as of 12:18, 13 February 2014
, 13 February 2014→Remaining bugs: force bugzilla refresh -.-
No edit summary |
(→Remaining bugs: force bugzilla refresh -.-) |
||
| Line 15: | Line 15: | ||
== Identifying and changing inline code patterns == | == Identifying and changing inline code patterns == | ||
The general advise is that we want to have separate files for Stylesheets (CSS), JavaScript (JS) and HTML. This means that any trace of JS and CSS in HTML is to be removed and replaced with something in an exising JS or CSS file. If there is no existing CSS or JS file, a new one has to be created: There are five types of code that need changing | The general advise is that we want to have separate files for Stylesheets (CSS), JavaScript (JS) and HTML. This means that any trace of JS and CSS in HTML is to be removed and replaced with something in an exising JS or CSS file. If there is no existing CSS or JS file, a new one has to be created: There are five types of code that need changing | ||
===JS in a script tag=== | ===JS in a script tag=== | ||