Author: jlltransac-533
Description:
The "Version Permanent Change" button which needs a confirmation is UNUSEFULL because it works exactly like the "NON permanent" button which does not need a confirmation. Both buttons are writing permanent cookies which are erased when users are cleaning the confidential datas. So, why two buttons ?
Version: --
Severity: minor
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T29719 Mobile broken for non-shortened URL | |||
| Resolved | None | T30510 Searching for terms with periods in the query string gives 403 errror - e.g. Data.gov | |||
| Resolved | None | T32517 Deprecate Ruby mobile gateway | |||
| Resolved | • Tfinc | T32518 Deprecate Hawhaw mobile gateway | |||
| Resolved | None | T32512 Turn MobileFrontend on for 100% of production traffic | |||
| Resolved | • Tfinc | T32336 'Classic Version Permanent Change' button is useless : it works exactly like NON permanent change |