RubinObservatory.org site issue with Chrome on macOS

Hello, Rubin website team-

This is to report a minor website issue I’m experiencing on macOS Sonoma (14.7.2) using the latest version of Chrome (updated just now; the issue existed before I updated as well). The problem also happens with Safari, so it may be a site code issue rather than a browser issue.

If I attempt to visit a page via the “burger” menu, the page will load, but the burger menu will remain open (at its top level), and the rendered page, while scrollable, is “dead” in the sense that none of the links on it will work. Perhaps the open menu is leaving it in an incompletely accessible state.

It happens when I attempt to access For Scientists > Events and deadlines > Rubin Science Assemblies. It also happens when I attempt to access the Early Science Program page, so it’s not unique to the RSA page. It also happens when I attempt to access the Press Releases page, so it’s not specific to the For Scientists menu.

If I reload the page, all is well. Similarly, if I copy the page URL and open it in a new tab, all is well. So the issue is not with the page contents. It’s probably a menu issue.

-Tom

Hi @TomLoredo , thanks for checking out the new rubinobservatory.org For Scientists pages and reporting this.

I can confirm this is my experience as well, though I had assumed it’s just how the right sidebar menu works – that it is the active panel while it is showing, until it is dismissed, after which the page content becomes interactive. But, when navigating by the top horizontal menu bar, page content is active and links can be clicked on even while the drop-down menu is showing. So there is a discrepancy in functionality between the right sidebar menu and top horizontal menu. Which does point to this perhaps being a bug or issue.

I’ll bring this to the attention of our website developers. Thanks again!

I think you pinpointed the problem—once a page was selected, the lower-level menus were automatically dismissed/closed, but not the top-level menu, which presumably was holding scope.

And, voila!, it’s already fixed! My thanks to all involved for the quick fix!

Yes! It turned out that this was a known issue and that a fix was already on the way – but we still appreciate the bug report :slight_smile: thanks again Tom.