Remove IE specific checks from default themes in Twenty Sixteen

[metodiew]

Remove IE specific checks from default themes in Twenty Sixteen

Trac ticket: 56699

[sabernhardt]

Please restore the .widecolumn class period, restore the full comments, and remove the new space before .updated:not(.published).

[sabernhardt]

This line needs to use wp_register_script. I missed that earlier.

[metodiew]

you are right, not sure how I missed that as well, updated!

[khansahan9864]

If you're working with a website or web application and want to remove conditional checks or styles specifically targeting Internet Explorer, you can follow these general steps:

Identify IE-specific code:
Look through your CSS files and HTML templates for code that is specifically targeting Internet Explorer. This might include conditional comments, IE-specific CSS rules, or JavaScript checks.

Remove conditional comments:
In older versions of HTML, conditional comments were used to target specific versions of Internet Explorer. If you find these in your code, you can safely remove them. For example:

{{{
#!html





}}}

Update CSS rules:
Look for CSS rules that are specifically written for Internet Explorer and remove them. Modern browsers usually have better support for web standards, so many of these rules may no longer be necessary.

Test in multiple browsers:
After making changes, thoroughly test your website or application in multiple browsers (Chrome, Firefox, Safari, Edge, etc.) to ensure that removing IE-specific code doesn't introduce new issues.

Consider using feature detection:
Instead of targeting specific browsers, consider using feature detection with JavaScript libraries like Modernizr. This allows you to detect browser capabilities and apply styles or functionality based on features rather than specific browser versions.

Update JavaScript checks:
If your code includes JavaScript checks for IE-specific features, you might want to update or remove them. Modern browsers have improved compatibility, reducing the need for browser-specific JavaScript code.

Check compatibility mode:
If you're working with a legacy application, make sure it's not running in compatibility mode for Internet Explorer. This mode can cause the browser to behave as an older version and may require specific code for compatibility.

Always keep in mind the importance of testing across different browsers and versions after making changes to ensure a consistent and functional user experience.