- Issue created by @finnsky
- Status changed to Needs review
7 months ago 1:52pm 13 May 2024 - Status changed to Needs work
7 months ago 2:22pm 24 May 2024 The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.
- Status changed to Needs review
7 months ago 2:35pm 24 May 2024 - Status changed to Needs work
4 months ago 6:12pm 14 August 2024 - 🇺🇸United States smustgrave
Wasn't entire sure how to test this one.
I applied the MR and tested on a view page which has dialog and didn't see any issue
If any other recommendation can try that.Did leave a comment on the MR for deprecation version.
- First commit to issue fork.
- Status changed to Needs review
4 months ago 12:31pm 28 August 2024 - 🇮🇳India shalini_jha
I have addressed the mentioned feedback. While updating, I also noticed that the dialog-deprecation.js file had the same issue in line state 12.0.0, so I updated that as well. Please review.
- Status changed to Needs work
4 months ago 2:05pm 29 August 2024 - Status changed to Needs review
4 months ago 4:57pm 29 August 2024 - 🇷🇸Serbia finnsky
RE: #11
For test you may revert this MR changes in toolbar.js locally. and when you will open close toolbar on desktop it will trigger deprecation messages.
Also you need to set drupalSettings.suppressDeprecationErrors to true. Easiest way to do it
core/misc/drupal.js:564 in Drupal.deprecationError remove this condition`drupalSettings.suppressDeprecationErrors === false &&`
- Status changed to Needs work
4 months ago 10:57pm 29 August 2024 - 🇺🇸United States smustgrave
Seems to have a few test failures
Thanks for taking care of that version update for the deprecation message.
- Status changed to Needs review
3 months ago 6:49am 13 September 2024 - 🇷🇸Serbia finnsky
We have broken test in navigation module. If 2 or more data-once attributes presented. Fixed here.
- Status changed to RTBC
3 months ago 1:10pm 13 September 2024 - 🇺🇸United States smustgrave
Believe feedback has been addressed. Tested same way as did in #11
- 🇳🇿New Zealand quietone
@finnsky, Thanks for the continued work on javaScript,
The first thing I did was change the format of URL is issue summary so I can read the issue title. There is no proposed resolution to explain the scope of this change. Is it everywhere in core or not? But I am more concerned about the testing. There are steps for testing but they are different than the steps #15. And neither of those are what was done to test this issue. Because of that I am setting to NW for manual testing and updated the remaining steps.
Also, I read the change record and changed some formatting. Why is it ticked that this impacts "Site builders, administrators, editors"?