#26060 closed enhancement (fixed)
Add and utilize :nth-child() selectors rather than the .alt(ernate) classes
Reported by: | helen | Owned by: | helen |
---|---|---|---|
Milestone: | 4.2 | Priority: | normal |
Severity: | normal | Version: | |
Component: | General | Keywords: | 4.2-beta |
Focuses: | ui, administration | Cc: |
Description
Since the new-in-3.8 admin styling is more liberal in allowing IE7 and IE8 to gracefully degrade, we really are overdue to make the jump. This should fix issues with and future-proof list tables that are altered via AJAX, such as comments (#25060). Going to leave the classes in CSS for back-compat.
Attachments (3)
Change History (17)
This ticket was mentioned in Slack in #design by helen. View the logs.
10 years ago
#5
@
10 years ago
- Component changed from Administration to General
- Focuses administration added
- Milestone changed from Future Release to 4.2
- Priority changed from low to normal
- Type changed from defect (bug) to enhancement
#6
@
10 years ago
- Owner set to helen
- Resolution set to fixed
- Status changed from new to closed
In 31181:
#7
@
10 years ago
I am optimistic that the above commit fixes this particular ticket, but do please re-open if any issues are noticed (besides what is already documented in #25060).
#8
@
10 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
@helen
Since you invited to re-open, I will.
in inline-edit-post.js around line 136, you changed
$(t.what+id).hide().after(editRow);
to
$(t.what+id).hide().before(editRow).before('<tr class="hidden"></tr>');
Is there a particular reason to change from "after" to "before"?
In a plugin, I rely on the fact that the quick edit is inserted after. Of course I could adapt my plugin. But maybe I am not the only one. Would the following be ok for you?
$(t.what+id).hide().after('<tr class="hidden"></tr>').after(editRow);
Working on a patch - takes a while to go through all the list tables.