Problem/Motivation

text.js adds the Show summary/Hide summary links even if the text area is disabled. This does not make sense. Either the text element has a summary already - in which case it should be shown - or it doesn't - in which case it should not be shown.

In #2381147: Text and text with summary field default value config does not use the text_format schema type we are adding disabled textareas with a summary field to the Configuration Translation UI where this surfaces.

Proposed resolution

Check for the disabled and readonly attributes before adding those links.

Remaining tasks

User interface changes

API changes

None.

Beta phase evaluation

-->

Reference: https://www.drupal.org/core/beta-changes
Issue category Bug because the current user interaction is non-sensical
Issue priority Normal because this only appears in rare cases, e.g. when translating Text field default values (after #2381147: Text and text with summary field default value config does not use the text_format schema type)
Unfrozen changes Unfrozen because it only affects markup
Prioritized changes The main goal of this issue is usability.
Disruption Completely non-disruptive.
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jhedstrom’s picture

I tried to reproduce this using the Article node type by:

  1. Grant normal users ability to edit all nodes of the article type
  2. Add an article as user 1, setting input format to Full HTML
  3. Log in as a normal user, go to edit this article

The body field shows as disabled, but I don't see the Show summary link. Is this perhaps browser-specific?

tstoeckler’s picture

@jhedstrom: That behavior is provided by \Drupal\filter\Element\TextFormat::processFormat(). That also sets the #access property on the summary element to FALSE, so that it isn't rendered. Thus, the hide/show summary links are never shown. I think simply marking a textarea with a summary as disabled should be enough to disable the links.

jhedstrom’s picture

Status: Active » Needs review
FileSize
2.81 KB

This patch checks for readonly/disabled state before adding the button. There is probably a more elegant way to do this. I used the issue mentioned above to test.

jhedstrom’s picture

Adding a screenshot.

jhedstrom’s picture

Status: Needs review » Needs work
Issue tags: +Needs reroll
Nitesh Sethia’s picture

Status: Needs work » Needs review
FileSize
3.27 KB

Rerolled the patch and made some change in the JS.

Vidushi Mehta’s picture

@jhedstrom I have rectify the issue on my local setup but did not reproduce the issue.

Steps i have followed.

1. New D8 Installation.
2. Enable module - Language, Configuration Translation, Content Translation, Interface Translation.
3. Add language "catalan".
4. Edit Article content type.
url - admin/structure/types/manage/article/translate/ca/add , /admin/structure/types/manage/article/fields/node.article.body/translate/ca/add

here there are two url's, I have not found any default value disable body textfield as per your screenshot.

Let me know if i have missed any step to reproduce issue.

mgifford’s picture

Status: Needs review » Needs work

Patch needs re-roll.

dimaro’s picture

Rerolled #6.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

joelpittet’s picture

Status: Needs review » Needs work

The js- class prefixes shouldn't be replaced without reason in this patch, setting to needs work.

harsha012’s picture

Status: Needs work » Needs review
FileSize
2.45 KB

Re-rolled the patch to 8.4 version.

Status: Needs review » Needs work

The last submitted patch, 15: 2383805-15.patch, failed testing. View results

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.