Open bedardk opened 5 years ago
The wb-navcurr
CSS Class seem to be added by the server. The wb-navcurr plugin is designed in a way to be exclusively a helper plugin for other WET-BOEW plugin. Like wb-navcurr is a helper used by the WET menu plugin. It's special highlighted blue style come only from the menu plugin.
More analysis are required and its behaviour/purpose would need to be clarified.
Not sure how relevant left navs still are in GCWeb these days, but it looks this issue began when GCWeb replaced its old mega menu with its "MENU" dropdown.
While prepping wet-boew/wet-boew#9308, I noticed that the "wb-navcurr" class gets added to the current page's footer link in the WET theme, but doesn't in GCWeb. Both WET and GCWeb's footers use a hardcoded "wb-navcurr" class on a parent container, presumably to trigger the navcurrent plugin... but it doesn't actually do anything in practice.
What's really responsible for triggering the navcurrent plugin is WET's menu plugin:
So when the mega menu was dropped from GCWeb, navcurrent completely stopped working everywhere (i.e. "MENU" dropdown, section navigation and footer).
The wb-navcurr CSS Class seem to be added by the server.
This doesn't seem to have been the case. The "wb-navcurr" class wasn't hardcoded into the pages linked from the OP. It was dynamically added-in via the menu/navcurrent plugins.
Here are the Wayback Machine's snapshots of the OP's pages for reference:
@duboisp Should this issue be reclassified as a bug? It'd be great if navcurrent could be brought back to life in GCWeb.
In previous releases the current item in the local navigation menu was highlighted with the wb-navcurr class. This seems to be missing in the latest release but it is working on Canada.ca WMS version.
Possibly related to #1512
ex.:
https://www.canada.ca/en/immigration-refugees-citizenship/services/application/check-status.html https://wet-boew.github.io/themes-dist/GCWeb/localnav/task1/index-en.html