State of collapsing sections in admin sidebar isn't remembered properly

[caesarsgrunt]

If you expand or collapse any section of the admin sidebar whilst viewing a page from another section, then after going to another page the section with the page which you were viewing will be expanded. This is very annoying, and seems to have been introduced in 2.8 - I didn't have this problem in 2.7.

[janeforshort]

I agree it's annoying when this happens, though it seems to be browser dependent. Since no one has claimed this and submitted a patch, punting as we are now in beta.

[caesarsgrunt]

This is far worse now than it used to be; often opening completely unrelated menus on the next page load.

[caesarsgrunt]

Video by markjaquith (#11335) at ​http://s3.amazonaws.com/txfx/screencasts/menu-glitch.mp4.

[caesarsgrunt]

Replying to janeforshort:

I agree it's annoying when this happens, though it seems to be browser dependent.

I get this problem in Firefox, markjaquith gets it in Safari.

These are probably the most common browsers for accessing the WP backend, at least for WP.org.

I haven't tested it affects any other browsers.

[westi]

Fix for the issue. Sync the two selectors for jQuery

[westi]

Attached patch fixes the issue for me.

[caesarsgrunt]

That mostly fixes it for me, but one issue remains.

With the whole menu collapsed (default state), click on, say, Posts.

Now expand, say, Media, by clicking the arrow.

Now go to, say, Dashboard. You'll notice that Posts has been left expanded as well as Media.

Firefox 3.5.5, WP revision [12320]

[caesarsgrunt]

Fix for the issue, including wrongly expanding current section.

[caesarsgrunt]

I think this patch completely fixes the issue, including the problem described in my last comment.

It also makes it impossible to store the status of the current section, but that was more or less a bug anyway - the section was open just from visiting it, but to store it as open you had to close it and open it again. Better without.

Try it and see what you think.

Moving this back to 2.9, since it's a simple bugfix for a major bug and has a patch.

[markjaquith]

(In [12334]) Fix the case of the curiously expanding wp-admin menu. props westi. fixes #10366

[caesarsgrunt]

Westi's patch, which you've committed, doesn't fix the entire issue, though it fixes most of it.

My patch fixed the whole thing...

[westi]

Replying to caesarsgrunt:

Westi's patch, which you've committed, doesn't fix the entire issue, though it fixes most of it.

My patch fixed the whole thing...

Can you detail how this is still broken and in which browsers you have tested please.

[caesarsgrunt]

Replying to westi:

Can you detail how this is still broken and in which browsers you have tested please.

Replying to caesarsgrunt:

With the whole menu collapsed (default state), click on, say, Posts.

Now expand, say, Media, by clicking the arrow.

Now go to, say, Dashboard. You'll notice that Posts has been left expanded as well as Media.

Firefox 3.5.5, WP revision [12320]

Now obviously also tested with latest trunk (r12337).
Also tested in Safari 4, but if you look at the code (see my patch 10366.2.diff) then it's obvious that this issue would occur in all browsers which correctly interpreted the code.

[caesarsgrunt]

Just to make it clear, this applies to all sections, not just the example of Posts and Media.

[caesarsgrunt]

Updated patch for latest trunk

[westi]

With this patch attached the following is now broken:

• Menus appear to work ok if you are on the dashboard.
• If you are on Posts and Expand links and refresh the page Media gets expanded.\

I think the issue you are trying to remove is the memory of the current page subment being open when you switch pages only if you expand another submenu while on that page?

Maybe that should be a new ticket for 3.0 as the current change is a significant improvement over the jumping menus.

Please could you open a new ticket for that.

[caesarsgrunt]

Replying to westi:

• If you are on Posts and Expand links and refresh the page Media gets expanded.\

I don't get this problem. I don't see how it could be caused by this patch, anyway.

Yes, I could open a different ticket for 3.0 if you want, but it is part of the same issue and is easily fixed. There's no reason not to do it for 2.9 that I can see.

[caesarsgrunt]

Another thought - are you sure you are using latest trunk (IE with the first patch comitted)? The issue you are describing sounds like it's the original issue which your first patch fixed.

[azaozz]

(In [12347]) Save menu sections' opened/closed state separately, fixes #10366