View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
3933 | Composr testing platform / automation goals | General / Uncategorised | public | 2019-10-29 18:03 | 2022-11-10 01:15 |
Reporter | Chris Graham | Assigned To | Guest | ||
Priority | normal | Severity | feature | ||
Status | new | Resolution | open | ||
Summary | 3933: Implement JS validation for modern browser API base | ||||
Description | I think currently for Composr internal validation we are not doing API checks, otherwise it'd be failing because there are a lot of JS core functions available since the JS validation code was written. Ideally we'd rebase the JS API to what is in our minimum IE/Edge version, and re-enable. Or maybe we should just stop doing API checks of the standard JavaScript library and leave that to ESLint. | ||||
Tags | Type: JavaScript, Type: Standards compliance | ||||
Attach Tags | |||||
Time estimation (hours) | 4 | ||||
Sponsorship open | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2019-10-29 18:03 | Chris Graham | New Issue | |
2019-11-14 21:49 | Chris Graham | Tag Attached: Type: Standards compliance | |
2019-12-05 15:43 | Chris Graham | Description Updated | |
2019-12-06 02:14 | Chris Graham | Project | Composr => Composr testing platform / automation goals |
2019-12-06 02:14 | Chris Graham | Category | core_webstandards => General |
2022-08-15 01:51 | Chris Graham | Summary | Further JS validation => Implement JS validation for modern browser API base |
2022-11-10 01:15 | Chris Graham | Tag Attached: Type: JavaScript | |
2023-02-26 18:29 | Chris Graham | Category | General => General / Uncategorised |