Can't seem to get the module to work and unclear of expected behavior

Created on 7 September 2023, over 1 year ago
Updated 12 September 2023, over 1 year ago

Problem/Motivation

I can't seem to get the module to work and I'm not entirely clear on the expected behavior. As of the moment, I'm not seeing the module apply any responsive behavior, regardless of text format/editor.

Steps to reproduce

To test, I tried the following in a fresh local environment with DDEV, PHP 8.1 and Drupal 10.1.3:

  1. Install and enable the latest version of the module, 1.18.
  2. Enable Basic HTML format on the Article content type.
  3. In the Basic HTML text format configuration with CKEditor 5 selected as the editor:
    • Add the Table plugin to the active toolbar.
    • Enable the "Apply responsive behavior to HTML tables" filter.
    • Disable all other filters.
  4. Create a new Article and add a table to the body using the Basic HTML format. Note that the table is not responsive (no tablesaw classes added).
  5. Save the Article. Note that the table is not responsive.

Additionally, I tested with the Plain Text format and no classes were added to a manually created HTML table after saving the node.

Is there something I'm missing in the config -- or an issue with how CKEditor 5 is processing/handling the WYSIWYG markup?

Thanks in advance!

πŸ’¬ Support request
Status

Closed: works as designed

Version

1.0

Component

Documentation

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Well, this turned out to be an issue on my part: I was creating new tables without a <thead> and, in its absence, the tablesaw classes were not applied. Tables created with the header row render responsive as expected. Please feel free to close out. Thanks!

  • Status changed to Closed: works as designed over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States mark_fullmer Tucson

    Thanks for clarifying! I've updated the text on the project overview page to clarify that a <thead> element *must* be present.

Production build 0.71.5 2024