The technical requirement is always at AEM level not at feature level Technical Requirements
All the features of AEM 6.3 would work if you are maintaining the technical requirement of AEM 6.3. We don’t have a list of a support clients’ OS, it’s only the list of a supported browsers. I can only say, that Windows 7 is an obsolete SO and even Microsoft does not support it anymore. We will rely on vendors choice
Supported Browsers for Authoring User Interface
| Browser | Support for UI
| Support for Classic UI |
| Google Chrome (Evergreen) | A: Supported | A: Supported |
| Microsoft Edge (Evergreen) | A: Supported (1) | A: Supported |
| Microsoft Internet Explorer 11 | A: Supported (1) | A: Supported |
| Mozilla Firefox (Evergreen) | A: Supported | A: Supported |
| Mozilla Firefox last ESR (3) | A: Supported | A: Supported |
| Apple Safari 10.x on macOS | A: Supported | A: Supported |
| Apple Safari 9 on OS X | Z: Not supported | Z: Not supported |
| Apple Safari on iOS 10.x (1,4) | A: Supported | Z: Not supported |
| Apple Safari on iOS 9 | Z: Not supported | Z: Not supported |
| Native Android Browser (5) | A: Supported | A: Supported |
Supported Browsers for Websites
Generally, the browser support level for sites is depending on the implementation of the templates, design and component output, and therefore in control of the party implementing these parts.
Note: Some browser-related exceptions for mobile clients are as listed below. These exceptions are only for AEM Forms:
Forms Portal is supported on Safari on iPad only. Blackberry browser supports only adaptive forms.
Also make sure to have a look at the link if you are accessing via Dispatcher The Dispatcher Security Checklist
For the CSRF token, if you are dependant on the granite.jquery clientlib, then it should be available by default. Else, you need to add granite.csrf.standalone dependency in your client library so as to enable the CSRF framework The CSRF Protection Framework
