Page MenuHomePhabricator

Wikivoyage: Deselect all listings at once
Closed, DeclinedPublicFeature

Description

Feature summary
I want to be able to deselect all listings at once in the layers section.

Wikivoyage uses listings to list attractions and monuments, activities, shops, restaurants, bars and lodgings under the See, Do, Buy, Eat, Drink and Sleep sections respectively.
On a Kartographer map, these listings can be shown or hidden collectively by type via the "layer" section on the right side.

Bildschirmfoto 2023-03-22 um 13.30.31.png (536×657 px, 169 KB)

Use case(s)

  • I just want to see one kind of listing, or just articles.
  • I have to deselect all other types individually.
  • Especially on maps with many types of listings (example), this takes a lot of time.

Bildschirmfoto 2023-03-22 um 13.30.48.png (1×2 px, 1 MB)

Wish

  • Add an option to deselect all listings.

Benefits

  • Saves time

Source of this request: https://meta.wikimedia.org/wiki/Talk:WMDE_Technical_Wishes/Geoinformation/Nearby_articles#My_two_cents

Event Timeline

Seems like a potential hackathon project to me. If it's not, feel free to remove the project tag.

This seems like a recent change... it used to be that only the groups used on the page by the map link/mapframe functions would be listed, but it seems now all categories that are defined are added to the list even when unused, making it very very long ? This might be due to a change in how the group parameter is being handled by the parser function ?

This seems like a recent change... it used to be that only the groups used on the page by the map link/mapframe functions would be listed, but it seems now all categories that are defined are added to the list even when unused, making it very very long ? This might be due to a change in how the group parameter is being handled by the parser function ?

Sounds like T332661?

IMHO, even if only the used types of listings were shown in the list, the request would still remain valid, because some articles can use lots of different types, resulting in a long list as well.

From the feedback on the page, i don't see a direct need right now and I don't think it is worth it to invest much time into this.

If someone has a patch, you are welcome to link it to this ticket however.