Change Details

The ReferenceTooltips and NavigationPopups gadgets add a similar behavior to wikis like #page-previews and #reference_previews do. That's why the code detects if on of these is enabled by the user and the disable the according feature in the extension. To do that the extension needs to know the local name of the gadget. This list is maintained in the production settings files in `wgPopupsConflictingRefTooltipsGadgetName` and `wgPopupsConflictingNavPopupsGadgetName` We also would like to know which projects have the ReferenceTooltips gadget enabled by default to eventually reach out when the #reference_previews feature is deployed. **Acceptance criteria:** [] Check the current list of local gadget names configured and update it for new/missing names [1] [2] [3] [] Leave out wikis that don't have the #page-previews extension enabled [] Check which projects have the ReferenceTooltips gadget enabled as a default [1] https://global-search.toolforge.org/?q=rt-tooltipContent&regex=1&ignorecase=1&namespaces=8&title=Gadget-.*%5C.js * [2] https://global-search.toolforge.org/?q=newNavpopup&regex=1&ignorecase=1&namespaces=8&title=Gadget-.*%5C.js * *) This search does not include results where the gadget scripts include the code from a different source. [3] https://gitlab.com/wmde/technical-wishes/gadget-checker

The ReferenceTooltips and NavigationPopups gadgets add a similar behavior to wikis like #page-previews and #reference_previews do. That's why the code detects if on of these is enabled by the user and the disable the according feature in the extension. To do that the extension needs to know the local name of the gadget. This list is maintained in the production settings files in `wgPopupsConflictingRefTooltipsGadgetName` and `wgPopupsConflictingNavPopupsGadgetName` We also would like to know which projects have the ReferenceTooltips gadget enabled by default to eventually reach out when the #reference_previews feature is deployed. **Acceptance criteria:** [x] Check the current list of local gadget names configured and update it for new/missing names [1] [2] [3] [x] Leave out wikis that don't have the #page-previews extension enabled [] Check which projects have the ReferenceTooltips gadget enabled as a default [1] https://global-search.toolforge.org/?q=rt-tooltipContent&regex=1&ignorecase=1&namespaces=8&title=Gadget-.*%5C.js * [2] https://global-search.toolforge.org/?q=newNavpopup&regex=1&ignorecase=1&namespaces=8&title=Gadget-.*%5C.js * *) This search does not include results where the gadget scripts include the code from a different source. [3] https://gitlab.com/wmde/technical-wishes/gadget-checker

The ReferenceTooltips and NavigationPopups gadgets add a similar behavior to wikis like #page-previews and #reference_previews do. That's why the code detects if on of these is enabled by the user and the disable the according feature in the extension. To do that the extension needs to know the local name of the gadget. This list is maintained in the production settings files in `wgPopupsConflictingRefTooltipsGadgetName` and `wgPopupsConflictingNavPopupsGadgetName` We also would like to know which projects have the ReferenceTooltips gadget enabled by default to eventually reach out when the #reference_previews feature is deployed. **Acceptance criteria:** [x] Check the current list of local gadget names configured and update it for new/missing names [1] [2] [3] [x] Leave out wikis that don't have the #page-previews extension enabled [] Check which projects have the ReferenceTooltips gadget enabled as a default [1] https://global-search.toolforge.org/?q=rt-tooltipContent&regex=1&ignorecase=1&namespaces=8&title=Gadget-.*%5C.js * [2] https://global-search.toolforge.org/?q=newNavpopup&regex=1&ignorecase=1&namespaces=8&title=Gadget-.*%5C.js * *) This search does not include results where the gadget scripts include the code from a different source. [3] https://gitlab.com/wmde/technical-wishes/gadget-checker