Opened 3 years ago
Closed 7 weeks ago
#56403 closed defect (bug) (wontfix)
Write 'Activated' instead of 'Installed' for activated theme
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Themes | Keywords: | reporter-feedback has-patch close |
| Focuses: | javascript | Cc: |
Description
On theme-install page, there have text for all installed theme but it should be 'Activated' instead of 'Installed' for activated theme.
Attachments (6)
Change History (12)
#1
@
3 years ago
- Component changed from Text Changes to Themes
- Owner set to audrasjb
- Status changed from new to reviewing
- Type changed from enhancement to defect (bug)
- Version trunk deleted
#2
@
3 years ago
- Keywords reporter-feedback added
Hello @alireyad welcome to WordPress Core Trac and thank you for opening this ticket,
I may be misunderstanding the issue, but the current implementation looks good to me. There's a difference between:
- Installed themes (may be several items)
- Installed AND activated theme (only one item).
#3
@
3 years ago
- Keywords has-patch added
Alright, but I have some concerns about duplicating the "Active/Activated" mention. See screenshot below.
Please note that the patch contains some unrelated file changes (but it can eventually be cleaned up before commit).
#4
@
3 years ago
Hi there, welcome to WordPress Trac! Thanks for the ticket!
I think I agree with @audrasjb here. For the purpose of the Add Themes screen, the relevant information to know is which themes are already installed, and the activated theme is already marked as such next to the theme name.
So the current implementation makes sense to me and I'm not sure if it needs any changes.
#5
@
3 years ago
Yes, activate button which is disabled for activated theme is not focusable. So I think, 'Activated' text instead of 'Installed' would be more focusable because upper part is focused for activated and installed theme.
On the other hand, it also will match with themes page.
#6
@
7 weeks ago
- Keywords close added
- Milestone Awaiting Review deleted
- Resolution set to wontfix
- Status changed from reviewing to closed
I think for now the consensus is to keep this. Whilst I understand you are preferring a change @alireyad there has to be a very good reason to adjust this as whilst feels a minor experience improvement for you it would impact a lot of documentation and might harm flows.
Let’s for now close this and look at a wider discussion. Not saying we can’t do that but we need to move on.
Current implementation