#Usability

As the screenshot shows: this works, except that the radios are not actually clickable. IOW: it shows the expected form, but it doesn't work.

It looks like 📌 Get Options as buttons in Page Data form working Active might help get us to a point where this is (close to) working!

Came across this triaging issues for Bug Smash Initiative and have a few thoughts:

1. Since we're moving to Navigation module I checked if that is also affected and it is
2. Since Claro and Starterkit Theme are unaffected should we really be fixing it for Stark?
3. As per bnjmnm a stylesheet is certainly better than a style attribute. Not just for customisations, but for Content Security Policy also.
4. I don't think toolbar.module is the right component for this since the issue is really with the dialog. Probably Javascript or Stark would be better. Even if it's a css fix, it's a javascript component we're styling.

Just to confirm, this is still an issue with the latest release of Drupal 11.

Came up as a daily BSI target but still seems #31 applies.

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

There hasn't been work on this for 11 years. Is there interest in pursuing this?

More information was asked for 8 years ago and it has not been supplied. Due to lack of interest I am closing this issue.

If you are interested in this idea, open a new issue in the core issue queue and add this issue as a related issue.

@grienauer noted that aside removing the css asset from the libraries.yml, it "might be" a good idea to also remove the css assets in the first place as well. ^^ completely forgot about that detail.

wim leers → credited pdureau → .

Fixing markup.

And crediting @pdureau, for our collaboration at DrupalCon Atlanta to ensure XB and UI Patterns 2 are aligned 😊

Config schema changes necessary for XB's JavaScriptComponent config entities attached to help get this going 👍

We don't have dropbuttons for saving anymore so we need a title and IS update here.

Also #19 is probably going to cause massive confusion over this if that wasn't also taken into account.

There has been no discussion here for 12 years, and of course, things have changed a bit in those years. Due to the lack of activity I am going to close this issue.

If there is anything in this issue that still need work, open a new issue and let's start fresh. As always, search for a duplicate issue first.

Thanks.

keondra. I'm not sure if you saw this comment in the Project Browser channel from chisfromredfin:

Yes, you can make those decisions and when we review we will discuss. I would borrow from the media library list view as much as possible, and I would keep the fields we have to the extent possible (though I imagine some might combine into one column)

Worked with Dawain on this during contribution day, Adding Atlanta2025 tag

Since there hasn't been a follow up going to close out, if still an issue in D11 please reopen

Thanks all!

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

Hiding patches and moving back to Active as the changes there don't line up with what is being discussed in comments. It seems like the consensus landed on having this configurable per entity type (and maybe bundle)? But we still need an IS update.

Is this something we still can/want to/should consider?

i've assigned the issue to myself and already created a MR.. Will work on an initial draft the next few days...

Turns out the skipto.css file was unnecessary to add and that additional css was causing all those issue. the three issues listed in the issue summary as well as the problems with the plus suite are solved with MR3. i was only unable to reproduce the problem with the status messages so far but odds are it might be solved as well.

I have to add I also noticed two more issues, but those were only one time and i was unable to reproduce so far, but i'll add them in the context of this issue cuz the "might" be at least related as well:

• Installing the plus suite with layout builder plus, navigation plus, and edit plus alongside skipto made the topbar not showing up and the edit button in the navigation sidebar was shown neither. after several installs and uninstalls both coexisted but it felt flaky.
• the skipto button and the expanded menu collided somehow with status messages and the display of the two in combination was off.

Seems pretty straight forward.

Is creating those URLs something for the drupal.org customization project?

Rolled into an MR.

I think the decision on whether this makes sense is valid when sites implement hook_user_format_name_alter, however those sites could simply turn it off?

I don't think we need tests here as we're just toggling on sorting - this should be tested elsewhere.

I don't think we need profiling here as the db query is simple.

This field type and widget is being deprecated and moved out of core eventually, do we want to bother working on the wording of it? 🌱 [Meta] Deprecate text_with_summary Active

I updated the MR so it's against 11.x. It works, but the code is just copy/pasted so it needs to be updated for modern coding standards. IS still needs updated as noted in a previous commit.

capysara → changed the visibility of the branch 711735-block-filter-category-11 to hidden.

I was still getting the error from #112 after adding the patch from #119 on 10.4.5. Turns out when submitting the form values to the plugin config, it was trying to set the "styles" setting outside of the "properties" array. This patch fixes that.

capysara → changed the visibility of the branch 11.x to hidden.

I am a first time user of this module testing at ALT2025 DrupalCon General contributor session.

Personally, I would prefer to list all of the modules by default (nothing selected) with the Recommended filters link available. Initially when I clicked on Recommended Filters but nothing appears to happens (since it was already set by default). I wasn't sure if the link was broken, but it wasn't after someone explained the purpose of the link.

If the Recommended filters link is clicked, the first two checkboxes (Only show projects covered by a security policy, Only show actively maintained projects) are checked and the Clear filters link should appear.

The Clear filter link should only appear (assuming the Recommended filter isn't checked by default):
- after a search has been performed
- the user makes selection in the Filter by category filter.
- Clicked the Recommended filters link

It would be helpful if the Recommended filter would have tooltip to indicate that the link will display modules are actively maintained.

I would like to see the Clear Filters and Recommended filters be buttons and not links. It was easy to overlook them at first until I looked more closely when I needed to locate them.

If you are going to keep the default set to display the recommended filtered modules, it would be helpful to know the recommended modules were already selected by default disable the link until they clicked the clear filter link.

Better yet, only include a list with all the modules that meet your criteria of recommended filters so you would have no need for the Recommended filters link. If they wanted something unsupported then send them to Drupal.org.

Based on Comment #27, the status should still be NW.

I rebased the MR. One change that got lost is replacing "Choose an option below" with "Choose an option". I think that #3386762 changed it to "Choose a field type":

I think that is good.

I did not test much, but I did look at the Reference options, and I think our changes are still there.

The MR needs a rebase after ✨ Use modal in add new field flow Active went in

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

AVIF is expensive (x2-x3 vs WEBP on compression) so fits for hires images mostly

I am working on this as a part of #Atlanta2025

While AVIF is better for compression, I am finding it hard to come to a conclusion as to whether AVIF is a good recommendation vs WEBP purely from an environmental impact of power consumption perspective. I.e., the power needeed to compress/decompress WEBP seems to be compared to PNG, but all I can find is random blog posts without any quantitative analysis that keep saying AVIF compress/decompress is more expensive, outweighing the savings from reduced data transfer/bandwidth. I really find it hard to find anything conclusive though - has anyone else looked into it from that perspective?

Thanks!

The only change since I last supported this 12 years ago is an S (and "documentation" = "docs"):

httpS://drupal.org/docs/modules/[project-name]

And the current URL for these pages are:

https://www.drupal.org/docs/extending-drupal/contributed-modules/contributed-module-documentation/[project-name]

which is terrible, and depends on me making sure people create doc guides with titles that match the project name. (I have discussed all of this other places.)

I think that we should use http://drupal.org/documentation/modules/[project-name] as path alias for a module's documentation page. It would avoid going to the project page and clicking on the documentation link given there.