- Issue created by @sagesolutions
- Status changed to Postponed: needs info
almost 2 years ago 5:57pm 1 September 2023 - 🇺🇸United States smustgrave
Believe the original purpose of adding that was to avoid users uploading tables for layout purposes that could cause accessibility issues.
But you do have the ability to hush certain fields have you tried that?
- Status changed to Active
almost 2 years ago 6:11pm 1 September 2023 - 🇺🇸United States greggles Denver, Colorado, USA
There was a time when certain td tags could be abused for xss more readily than other tags. I think that's likely outdated and we could definitely consider removing that tag.
Updating the issue to match that status.
- 🇺🇸United States smustgrave
Thanks @greggles if we remove td should table also be removed?
Only reason I could think for checking is accessibility which may be out of this module.
- 🇺🇸United States greggles Denver, Colorado, USA
yep, makes sense.
And agreed that a11y is outside the scope here.
- 🇮🇳India chetan 11
From preventing this issue, we just need to remove the permission from anonymous user.
un-check the anonymous user in the table editor, attaching the screenshot for the reference.
This error will not occur again. - Status changed to Needs review
almost 2 years ago 1:12pm 19 September 2023 - Status changed to Active
almost 2 years ago 3:40pm 19 September 2023 - 🇺🇸United States greggles Denver, Colorado, USA
This issue is about removing the warning for TD and TABLE tags from the code.
We need a patch or merge request for it to get to "needs review".
- last update
over 1 year ago 15 pass - @smustgrave opened merge request.
-
smustgrave →
committed 0bb5ab16 on 2.0.x
Issue #3372969: Remove the TD and TABLE tags as particularly dangerous...
-
smustgrave →
committed 0bb5ab16 on 2.0.x
- Status changed to Fixed
over 1 year ago 10:51pm 9 November 2023 Automatically closed - issue fixed for 2 weeks with no activity.