Making WordPress.org

Opened 16 months ago

Closed 3 months ago

#6564 closed feature request (wontfix)

The options in the select box must contain a placeholder

Reported by: aezazshekh's profile aezazshekh Owned by:
Milestone: Priority: normal
Component: Trac Keywords: needs-patch has-screenshots close 2nd-opinion
Cc:

Description

When we open the Custom Query page, the first option in all the select boxes is blank. So instead of the blank option, we should add that placeholder option.

Custom Query page => https://meta.trac.wordpress.org/query

Attachments (1)

CleanShot 2022-11-02 at 18.04.08@2x.png (978.8 KB) - added by aezazshekh 16 months ago.
Screenshot of Issue

Download all attachments as: .zip

Change History (4)

@aezazshekh
16 months ago

Screenshot of Issue

#1 @aezazshekh
16 months ago

For example, I have added a placeholder in a select box here.

Screenshot of the Example
https://share.cleanshot.com/TNIh8ioIaOxNuhWzWlnQ

#2 @dd32
16 months ago

  • Keywords close 2nd-opinion added

This is not something we can realistically do, as the Trac software generates these for us.

This should be reported as a bug to Trac itself via https://trac.edgewall.org/

That being said, we can prefix an element to all <select>s via Javascript (or Trac Genshi template rewrites I guess), but would require someone to go through and make a HTML ID => Default text mapping, and at that point I'm really starting to question if the effort is worth it.

(edit: Also; a lot of those selects don't have a clear singular text, the context is provided more-or-less by the text around it, rather than the contents. The Component select is probably the only one it can be easily done for, and even then, not selecting a component is a valid query sometimes)

I'm marking this as 2nd-opinion close instead of just closing this as wontfix, unless someone feels super strongly about this.

Last edited 16 months ago by dd32 (previous) (diff)

#3 @coffee2code
3 months ago

  • Resolution set to wontfix
  • Status changed from new to closed

I agree with Dion. I don't think this is worth the effort, especially since it's not straightforward, it only realistically applies to one or two selects, and context seems sufficient to infer the meaning of the inputs.

Note: See TracTickets for help on using tickets.