Postponed (maintainer needs more info)
Project:
Claro
Version:
3.0.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Jul 2023 at 09:28 UTC
Updated:
21 Sep 2026 at 15:26 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
gauravvvv commentedI have changed the textfield for weight to select list, attached patch for same. please review thanks
Comment #3
smustgrave commentedCan we add a simple assertion to check if it's a select list.
Comment #4
kostyashupenkoPatch is working
Comment #5
lauriiiWhat happens if someone has set arbitrary numerical values for the weight using the textfield? Wouldn't that break when we change to a select?
Comment #6
smustgrave commentedMoving to NW as the tests tag was removed without adding anything
Comment #7
gauravvvv commentedHi @lauriii, if we input an arbitrary numerical value in the weight using a text field, it automatically adjusts to the closest available value. For example, if we enter 15.2, it will change to 15, or to the next available value if any are present before 15.
Comment #11
quietone commentedThe Claro theme was approved for removal in #3576460: [policy, no patch] Deprecate and remove Claro.
This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
The deprecation work is in #3576668: [meta] Tasks to deprecate Claro and the removal work in #3584638: [meta] Tasks to remove the Claro theme.
Comment #12
quietone commentedComment #13
smustgrave commentedClaro has moved to contrib
Not sure I agree with it needing to be a dropdown? What's the reason?