When searching the issue queue:
https://git7site.devdrupal.org/project/issues/search

The Issue tags have form elements and the label tags just don't match up for edit-vocabulary-9-op:

<div id="edit-vocabulary-9-wrapper" class="views-exposed-widget views-widget-filter-vocabulary_9">
<label for="edit-vocabulary-9"> Issue tags </label>
<div class="views-operator">
<div class="form-item form-type-select form-item-vocabulary-9-op">
<select id="edit-vocabulary-9-op" class="form-select" name="vocabulary_9_op">events=Object { change=[1], click=[1], blur=[1], more...}handle=function()
</div>
</div>
<div class="views-widget">
<div class="form-item form-type-textfield form-item-vocabulary-9" role="application">
<input id="edit-vocabulary-9" class="form-text form-autocomplete" type="text" maxlength="128" size="32" value="" name="vocabulary_9" autocomplete="OFF" aria-autocomplete="list">events=Object { change=[1], click=[1], blur=[2], more...}handle=function()
<input id="edit-vocabulary-9-autocomplete" class="autocomplete autocomplete-processed" type="hidden" disabled="disabled" value="https://git7site.devdrupal.org/admin/views/ajax/autocomplete/taxonomy/9">events=Object { change=[1], click=[1], blur=[1], more...}handle=function()
<span id="edit-vocabulary-9-autocomplete-aria-live" class="element-invisible" aria-live="assertive"></span>
</div>
</div>

Issue fork drupal-2096013

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

mustanggb’s picture

Status: Active » Needs work

Confirmed, but perhaps you could tell us what is should be, which would make it an easier job to fix.

jthorson’s picture

Status: Needs work » Needs review
Issue tags: +drupal.org D7

I believe <label for="edit-vocabulary-9"> Issue tags </label> needs to show up immediately before the <input id="edit-vocabulary-9" ... tag, instead of outside of the container divs.

tvn’s picture

Project: [Archive] Drupal.org D7 upgrade QA » Project issue tracking
Version: » 7.x-2.x-dev
Component: Code » Issues
Status: Needs review » Needs work
Issue tags: -Accessibility, -drupal.org D7 +Drupal.org 7.1
mgifford’s picture

There are 3 form elements:
edit-vocabulary-9-op
edit-vocabulary-9
edit-vocabulary-9-autocomplete

Only one label <label for="edit-vocabulary-9">

Every input elements needs to be associated with a label.

Hope this helps.

drumm’s picture

Project: Project issue tracking » Views (for Drupal 7)
Version: 7.x-2.x-dev » 7.x-3.x-dev
Component: Issues » exposed filters

Issue queues use the usual Views exposed filters.

kalman.hosszu’s picture

Assigned: Unassigned » kalman.hosszu
Issue summary: View changes

I will check it

kalman.hosszu’s picture

Status: Needs work » Needs review
StatusFileSize
new1.95 KB
new66.69 KB

I attached the first version of the patch. It creates a new form item in operations for label and shows the exposed filters' #title attribute. I also attached a screenshot about the admin interface change.

Please review and tell me if something needs to be modified.

drumm’s picture

Status: Needs review » Needs work

'#title_display' => 'invisible' can be used to have the title be available for screen readers, and keep the visual UI the same.

  • Commit 5c5498b on 7.x-3.x authored by kalman.hosszu, committed by dawehner:
    Issue #2096013 by kalman.hosszu | mgifford: Issue Tag labels have...
dawehner’s picture

Issue tags: +VDC

I committed the patch, because it looked kinda nice, but haven't updated the browser in the meantime.
Let's work on a patch to hide the title as well.

kalman.hosszu’s picture

Status: Needs work » Needs review
StatusFileSize
new563 bytes

I created a small patch to hide the title.

dawehner’s picture

Project: Views (for Drupal 7) » Drupal core
Version: 7.x-3.x-dev » 9.x-dev
Component: exposed filters » ajax system
Status: Needs review » Patch (to be ported)

There we go.

dawehner’s picture

Version: 9.x-dev » 8.x-dev

.

drumm’s picture

Issue tags: -Drupal.org 7.1 +needs drupal.org deployment, +affects drupal.org

Thanks!

We already have a Views -dev upgrade coming up for #2128849: Module downloads listed as "gz" instead of "tar.gz" and #2138855: Module project index page - exposed fields don't work too. That should happen next week, when things are more quiet.

drumm’s picture

Issue tags: -needs drupal.org deployment +Accessibility

Now deployed on Drupal.org.

mgifford’s picture

@dawehner should this still be listed as "Patch (to be ported)"?

Seems like it's been a bit all over the place.

Not sure where in D8 the views_handler_filter() function currently is sitting.

dawehner’s picture

Status: Patch (to be ported) » Needs review
StatusFileSize
new2.71 KB

Just started a port.

Status: Needs review » Needs work

The last submitted patch, 17: vdc-2096013-17.patch, failed testing.

mgifford’s picture

Issue tags: +Needs reroll
mgifford’s picture

Status: Needs work » Needs review
Issue tags: -Needs reroll
StatusFileSize
new2.66 KB

File moved...

Status: Needs review » Needs work

The last submitted patch, 20: vdc-2096013-20.patch, failed testing.

mgifford’s picture

Status: Needs work » Needs review
StatusFileSize
new2.64 KB

reroll

Status: Needs review » Needs work

The last submitted patch, 22: vdc-2096013-22.patch, failed testing.

mgifford’s picture

Issue tags: +Needs tests

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

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

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.

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

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

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

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

larowlan’s picture

Component: ajax system » views.module
Issue tags: +Bug Smash Initiative
+++ b/core/modules/views/config/schema/views.data_types.schema.yml
@@ -700,6 +700,9 @@ views_filter:
         operator:
...
+        operator:

This is invalid YAML, there can't be two `operator:` keys

Triaged this as part of bug-smash, I think this belongs in the Views queue.

vsujeetkumar’s picture

Status: Needs work » Needs review
StatusFileSize
new2.5 KB

Re-roll patch given for 8.9.x and worked on #33, Updated 'operator' to 'operator_label'.
@larowlan Please have a look and advise.

bhumikavarshney’s picture

StatusFileSize
new44.66 KB

Hi @vsujeetkumar,
Thanks for the patch.
It works good for me and applies cleanly.

drumm’s picture

Title: Issue Tag labels have problems in issue queue search » Exposed filter operators should have field labels

Re-titling to be more-straightforward for what the core issue is.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Needs review » Needs work

This was previously tagged for tests in #24 which still need to happen.

Did not test for issue.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

sokru’s picture

Related issue has tests and upgrade path that this is missing. On Views admin UI the patches from this issue uses the same label "Operator label" as #3120627: Make views exposed filter operator labels configurable, either of them would need a change the label to avoid confusion.

arunkumark made their first commit to this issue’s fork.

arunkumark’s picture

Assigned: Unassigned » arunkumark

arunkumark’s picture

Status: Needs work » Needs review

Created MR from the patch #34 and created test case for the new field.

arunkumark’s picture

Assigned: arunkumark » Unassigned
arunkumark’s picture

sokru’s picture

Status: Needs review » Needs work

@arunmark thanks for the merge request, however this still needs the upgrade path and the config updates, similar to what has been done on #3120627: Make views exposed filter operator labels configurable.

arunkumark’s picture

@sokru
Thanks for the comment as suggested, I added Upgrade path for the patch. I was moving to Review.

arunkumark’s picture

Status: Needs work » Needs review
StatusFileSize
new788.36 KB
new691.11 KB

I verified the patch on the unit test on my local, It was working fine. Attached screenshot for reference.
Not sure why it's failing on the Automated test in Gitlab.

Pass
Pass

For now moving to review, If needed please move back to work.

smustgrave’s picture

Status: Needs review » Needs work

Your local probably isn’t 100% aligned with gitlab. Can’t be marked with a failing test

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.