Opened 11 years ago
Closed 7 weeks ago
#28734 closed defect (bug) (worksforme)
Back button doesn't work when in the theme previewer
Reported by: | iseulde | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.9 |
Component: | Themes | Keywords: | needs-patch |
Focuses: | administration | Cc: |
Description
To reproduce:
- Go to theme-install.php;
- Go to "popular", then to "featured" (clicking the back button here works);
- Click on "Details and Preview" for a theme;
- Click next;
- Click the browser's back button and you'll be pointed to theme-install.php.
Change History (5)
#2
@
10 years ago
- Keywords needs-patch added; reporter-feedback removed
- Milestone changed from Awaiting Review to Future Release
Yes, it does. Sometimes the URL updates in the browser, but the screen does not, other times is just goes back to theme-install.php. E.g. when I click the back button, the URL is updated from theme-install.php?theme=x to theme-install.php?browse=popular, but the screen does not update. Another click updates it to theme-install.php, but again nothing happens.
Related: #28735.
#4
@
10 years ago
Hello. I can duplicate this issue on 4.1. Could we tackle this with some jQuery?
$( window ).unload(function(event) { if ($('a.close-full-overlay').length > 0){ $('a.close-full-overlay').click(); } });
#5
@
7 weeks ago
- Resolution set to worksforme
- Status changed from new to closed
I am not able to reproduce this. I am using WordPress 6.7.1, Chrome and Firefox on Windows 11.
I could not find a tab called featured, so I clicked on Popular, then on Latest, and used the back button of the browser to return to Popular. This worked well.
Then I chose "Preview" on a classic theme and used the forward arrow button in the interface a couple of times. When I used the back button of the browser, the previous theme was shown in the previewer.
I was only returned to theme-install.php?browse=popular
once I had moved backwards past the first theme I had previewed.
I am not sure if I follow, anyway - does this still happen with 4.0?