Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tedbow created an issue. See original summary.

tedbow’s picture

Issue summary: View changes
GrandmaGlassesRopeMan’s picture

GrandmaGlassesRopeMan’s picture

Issue summary: View changes
andrewmacpherson’s picture

Tagging for my list.

I'm aware of a few outstanding a11y points which have been mentioned in various places, including some issues focused on the layout builder. We need to gather those up, and make separate actionable issues where appropriate.

I've also seen a lot of issues crop up (e.g. in the accessibility tag), where it's clear accessibility is being addressed by the settings tray contributors themselves, which is GREAT :-)

@tedbow:

A11y review & sign-off could be quicker if the maintainer walks me though the architecture, and point out what's been done for a11y already. I was following it during the very early stages, but lost track. In particular, I'm keen to learn how the dialog and off-canvas components differ now that they are separate. Could we find a time to meet in Slack/Skype/Hangouts for this?

tedbow’s picture

@andrewmacpherson thanks for tagging for your list.

Could we find a time to meet in Slack/Skype/Hangouts for this?

Yes definitely! Just contact via Drupal Slack, IRC, or my d.o contact form and we can setup a time.

tedbow’s picture

Issue summary: View changes
tedbow’s picture

tedbow’s picture

Issue summary: View changes

Reviewed #2773601: Display "You are now in edit mode" prompt when user enters edit mode with UX meeting. All agreed this should not a be blocker for the module being stable(and it might not be needed at all).

tedbow’s picture

Issue summary: View changes

Striking through issues that are done in the summary

We had

Manually test in all core themes

But the only core themes that available with testing flag turned on are Bartik, Seven and Stark.

I just tested Bartik and Stark. Seven doesn't apply because it removes contextual links.

The functional javascript testing in the module does cover 'bartik', 'stark', 'classy', 'stable'

tedbow’s picture

Issue summary: View changes

#2922603: Mark Settings Tray module as stable committed!!!

#2928409: [META] Accessibility issues for Settings Tray also just got it's last MUST-HAVE issue done: #2934178: Contrast issues with off-canvas dialog styling
So crossing if off to on this list as it should not be a blocker for Stable any more.

This leaves only #2919373: Prevent Settings Tray functionality for blocks that have configuration overrides which was RTBC but after a demo with @webchick it is not back to Needs Review for a patch addressing some changes she recommended.

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

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now 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.

tedbow’s picture

Issue summary: View changes
Status: Active » Needs review
FileSize
2.44 KB

Yay! #2919373: Prevent Settings Tray functionality for blocks that have configuration overrides was committed! There was small follow up #2938309: Only install Quick Edit when necessary for Settings Tray tests because of test failures with PostgreSQL

We probably also want to do #2896356: Move 'settings_tray' forms out of Settings Tray and into respective modules and annotations before this current issue but #2896356 only should be done if the module is going stable.

So I don't know if it would make sense to make it part of this patch. But leaving out for now this patch is smaller.

Wim Leers’s picture

🎉

tedbow’s picture

I should have remove "needs accessibility review" tag in #12, removed

tedbow’s picture

Wim Leers’s picture

Status: Needs review » Reviewed & tested by the community

Congrats!

xjm’s picture

Title: Mark Settings Tray module as stable » [Feb. 21] Mark Settings Tray module as stable
Status: Reviewed & tested by the community » Postponed

Thanks @Wim Leers and @tedbow!

This seems to be in good shape. We'll look at this again next month. (Marking postponed for now; it can just be set back to RTBC on Feb. 21.)

xjm’s picture

Title: [Feb. 21] Mark Settings Tray module as stable » Mark Settings Tray module as stable
Status: Postponed » Reviewed & tested by the community

Talked to catch and larowlan; we agreed we can go ahead with this now. Setting back to RTBC. :)

tedbow’s picture

I talked with @xjm who recommended that we bring in the patch in #2896356: Move 'settings_tray' forms out of Settings Tray and into respective modules and annotations (which is also RTBC) into this issue because those changes should only happen when the module goes stable.

Here is the combined patch.

Note to future self:
To make git find the copies use
git diff -M10% --find-copies-harder 8.6.x > ../2922603-21.patch
and set make sure gitconfig has diff.renames=copies

xjm’s picture

Adding credit to @Wim Leers here. His contribution on this issue is emoji but he reviewed the other. :)

xjm’s picture

Status: Reviewed & tested by the community » Needs review

It would be good to get a last +1 on this since I proposed the latest change and Ted rolled a patch. I pinged @tim.plunkett for a quick look since it touches core block implementations.

tim.plunkett’s picture

Status: Needs review » Reviewed & tested by the community

I personally don't like having the settings_tray keys in system.module blocks, but there is precedence for "use some optional module's annotation key in a core annotation": the field_ui_base_route flag on entity types.

So given that, I think this is fine. Re-RTBC.

  • xjm committed 7a012b1 on 8.6.x
    Issue #2922603 by tedbow, Wim Leers, andrewmacpherson: Mark Settings...
xjm’s picture

Priority: Normal » Major
Status: Reviewed & tested by the community » Fixed
Issue tags: +8.5.0 highlights

Thanks @tim.plunkett for the confirmation and slightly reluctant signoff. :)

The committers have discussed Settings Tray's status in several previous meetings and again in Slack today, and each time those discussing it were comfortable with Settings Tray being stable once the above issues were resolved, including backporting this between 8.5.0's alpha and beta (i.e. right now).

So let's do this!! ☃️💯💃🏻

Fixed the following on commit:

FILE: ...m/git/maintainer/core/modules/settings_tray/settings_tray.module
----------------------------------------------------------------------
FOUND 0 ERRORS AND 2 WARNINGS AFFECTING 2 LINES
----------------------------------------------------------------------
 12 | WARNING | [x] Unused use statement
 13 | WARNING | [x] Unused use statement
----------------------------------------------------------------------
PHPCBF CAN FIX THE 2 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------

Like so:

diff --git a/core/modules/settings_tray/settings_tray.module b/core/modules/settings_tray/settings_tray.module
index 114b4d9b2c..87b40ac66b 100644
--- a/core/modules/settings_tray/settings_tray.module
+++ b/core/modules/settings_tray/settings_tray.module
@@ -9,8 +9,6 @@
 use Drupal\Core\Routing\RouteMatchInterface;
 use Drupal\Core\Url;
 use Drupal\settings_tray\Block\BlockEntityOffCanvasForm;
-use Drupal\settings_tray\Form\SystemBrandingOffCanvasForm;
-use Drupal\settings_tray\Form\SystemMenuOffCanvasForm;
 use Drupal\block\entity\Block;
 use Drupal\block\BlockInterface;
 

Congratulations @tedbow and contributors!

  • xjm committed 553d91a on 8.5.x
    Issue #2922603 by tedbow, Wim Leers, andrewmacpherson: Mark Settings...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.