#58836 closed enhancement (fixed)
Remove IE specific checks from more default themes
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 6.9 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Bundled Theme | Keywords: | has-patch reporter-feedback commit |
| Focuses: | Cc: |
Description (last modified by )
Follow-up to #56699
Remove IE conditional statements and register external resources without enqueuing them for four more themes:
- Twenty Eleven
- Twenty Twelve
- Twenty Fourteen
- Twenty Sixteen
Also completes the removal these resources on
- Twenty Thirteen
- Twenty Fifteen
- Twenty Seventeen
Attachments (1)
Change History (51)
This ticket was mentioned in Slack in #core by oglekler. View the logs.
2 years ago
#4
@
22 months ago
- Keywords reporter-feedback removed
- Summary changed from Remove IE specific checks from more default themes (6.4) to Remove IE specific checks from more default themes
#56699 only committed changes to Twenty Thirteen, Twenty Fifteen and Twenty Seventeen.
The remaining pull requests on that ticket seem close to ready, but I still have not created child themes to test them.
- PR 3474 is probably closer to how Twenty Eleven should be changed than the other PR, though I would prefer to leave the
readme.txtandhtml5.jsintact. That can be refreshed now that [57886] is committed. Removing the IE7 styles would also fix #46771. - PR 4642 edits Twenty Twelve.
- PR 4644 edits Twenty Fourteen.
- PR 4658 edits Twenty Sixteen.
#6
@
19 months ago
@sabernhardt I am coming to this a little colder so wanted to get an update and see how we can progress. It seems we have 3 outstanding PRS that could relate to this - is that correct?
#7
@
19 months ago
- Keywords needs-testing-info added
- Owner set to sabernhardt
- Status changed from new to accepted
I need to create some child themes to test the patches, though I would like to add more changes. Genericons can be updated for Twenty Thirteen through Twenty Sixteen so the EOT file reference does not show console messages in Firefox (and at least the Instagram icon is newer). Plus, I remember planning to request a change to one of the PRs (I found my note later, and it involved Genericons).
Refreshing Twenty Eleven's patch needs to wait until after Tuesday due to version bumps, but the child themes should take longer than that anyway.
#8
@
18 months ago
Ok that sounds like a solid plan @sabernhardt and I am going to leave this with you for now then.
This ticket was mentioned in PR #7411 on WordPress/wordpress-develop by @sabernhardt.
16 months ago
#10
- Keywords has-patch added; needs-patch removed
Twenty Eleven changes:
- Removes IE conditional code and HTML5 Shiv from
header.php - Removes IE7 and IE8 sections from
style.cssandrtl.css - Removes
widthfromeditor-style.css - Removes extra
clipsyntax fromfunctions.phpandstyle.css - Removes
filterfromstyle.cssanddark.css - Removes IE8
width: autorule for full-size and large-size images instyle.css
Props: neychok
This ticket was mentioned in PR #7412 on WordPress/wordpress-develop by @sabernhardt.
16 months ago
#11
Twenty Twelve changes:
- Registers
ie.csswithout enqueuing it - Removes IE conditional code and HTML5 Shiv from
header.php - Removes
widthhack fromeditor-style.css - Removes extra
clipsyntax fromcustom-header.php
Props: metodiew
This ticket was mentioned in PR #7414 on WordPress/wordpress-develop by @sabernhardt.
16 months ago
#12
Twenty Fourteen changes:
- Registers
ie.csswithout enqueuing it - Removes IE conditional code and HTML5 Shiv from
header.php - Removes extra
clipsyntax fromcustom-header.php
Props: metodiew
This ticket was mentioned in PR #7416 on WordPress/wordpress-develop by @sabernhardt.
16 months ago
#13
Twenty Sixteen changes:
- Registers IE styles and HTML5 script without enqueuing them
- Removes IE fallback for RGBA colors in
customizer.phpand adds a semicolon
Props: metodiew
#14
@
16 months ago
The remaining pull requests from #56699 (that neychok and metodiew made) were mostly ready, but I wanted to connect all of them to this ticket in sequence.
I still should test a bit more before taking them out of draft status and uploading the child themes collection.
I think updating Genericons belongs on a separate ticket (#62128) because that should involve more than IE-related changes.
@
16 months ago
Child themes for testing Twenty Eleven, Twenty Twelve, Twenty Fourteen and Twenty Sixteen
This ticket was mentioned in Slack in #core by stoyangeorgiev. View the logs.
16 months ago
#17
@
16 months ago
- Keywords needs-testing added
- Milestone changed from 6.7 to 6.8
Moving to 6.8 for more testing
#18
@
14 months ago
Hi there! @metodiew and I are currently attending a contributor day in WordCamp Sofia 2024, and we're eager to help move this ticket forward. Would you be open to our assistance? We'd love to contribute and help make progress on this.
This ticket was mentioned in Slack in #core-test by krupajnanda. View the logs.
11 months ago
This ticket was mentioned in Slack in #core by audrasjb. View the logs.
11 months ago
#22
@
11 months ago
- Milestone changed from 6.8 to 6.9
As per today's bug scrub: It appears this ticket is still under review and needs testing. As 6.8 beta 1 is very close, I'm moving it to 6.9. Feel free to move it back to 6.8 if it can be committed by Monday.
#23
@
9 months ago
- Keywords needs-testing-info reporter-feedback added; needs-testing removed
@sabernhardt could you provide clear reproduction steps to understand what to expect before and after this patch?
#24
@
9 months ago
- Keywords needs-test-info added; needs-testing-info removed
Updating keyword to new version.
This ticket was mentioned in Slack in #core-test by boniu91. View the logs.
8 months ago
This ticket was mentioned in Slack in #core by welcher. View the logs.
4 months ago
#27
@
4 months ago
@sabernhardt this was reviewed in the 6.9 bug scrub. Do you think you can continue work on this for 6.9?
This ticket was mentioned in Slack in #core by wildworks. View the logs.
3 months ago
#29
@
3 months ago
This ticket was reviewed in today's 6.9 Bug Scrub again. This ticket needs testing instructions.
#30
@
3 months ago
- Keywords reviewing added; needs-test-info removed
- Owner changed from sabernhardt to joedolson
There isn't really any practical test for this other than install the themes and verify that there is no change. Hypothetically, you could install a version of IE<10 and verify that the fixes done for those browsers are no longer present, but I think that's unnecessary.
I'm going to take ownership of this ticket to test and prepare for commit. There won't be any need for screenshots, because this will only pass testing if there are no differences.
#31
@
3 months ago
- Keywords commit added; reviewing removed
Twenty Eleven: Verified; no IE-specific code present. No deprecation notice thrown in either context, as Twenty Eleven does not use conditional comments.
Twenty Twelve: Verified; deprecation notice thrown before patch, no deprecation notice after. No IE-specific code present.
Twenty Fourteen: Verified; deprecation notice thrown before patch, no deprecation notice after. No IE-specific code present.
Twenty Sixteen: Verified; four deprecation notices thrown before patch, none after. No IE-specific code present.
Marking for commit.
This ticket was mentioned in PR #10327 on WordPress/wordpress-develop by @sabernhardt.
3 months ago
#32
Twenty Seventeen changes:
- Removes conditional data and source from registered IE stylesheet
- Replaces contents of
ie.cssandhtml5.js - Removes HTML5 Shiv credit from
readme.txt
This ticket was mentioned in PR #10328 on WordPress/wordpress-develop by @sabernhardt.
3 months ago
#33
Twenty Fifteen changes:
- Removes conditional data and source from registered IE stylesheet
- Replaces contents of
ie.cssandhtml5.js - Removes HTML5 Shiv credit from
readme.txt
This ticket was mentioned in PR #10329 on WordPress/wordpress-develop by @sabernhardt.
3 months ago
#34
Twenty Thirteen changes:
- Removes conditional data and source from registered IE stylesheet
- Replaces contents of
ie.cssandhtml5.js - Removes HTML5 Shiv credit from
readme.txt
#35
@
3 months ago
- Description modified (diff)
Twenty Thirteen: Verified; deprecation error before patch, none after patch; obsolete code removed.
Twenty Fifteen: Verified; 2 deprecation errors before patch, none after patch; obsolete code removed.
Twenty Seventeen: Verified; 2 deprecation errors before patch, none after patch; obsolete code removed.
@sabernhardt commented on PR #7411:
3 months ago
#43
Committed in r60960
@sabernhardt commented on PR #7412:
3 months ago
#44
Committed in r60961
@sabernhardt commented on PR #10329:
3 months ago
#45
Committed in r60962
@sabernhardt commented on PR #7414:
3 months ago
#46
Committed in r60963
@sabernhardt commented on PR #10328:
3 months ago
#47
Committed in r60964
@sabernhardt commented on PR #7416:
3 months ago
#48
Committed in r60965
@sabernhardt commented on PR #10327:
3 months ago
#49
Committed in r60966
This ticket was discussed during a bug scrub.
@sabernhardt does there is still work to be done? If so, please clarify the scope, because #56699 is closed and had the same themes mentioned.
Add props to @mukesh27