As far as I know there is no generic AO+Safari problem bottapress, so there’s no general fix that I can apply to solve your issue.
That being said, there might be a problem in a specific context (the specific combination of CSS from theme + plugins).
So let’s start with some questions;
* what is general.css part of? your theme or a plugin? which one specifically?
* How did you come to the conclusion that the optimization of general.css is the problem? Does excluding it fix it?
* Is there any specific notice/ warning in Safari that confirms that the CSS is not recognized? If so, can you copy/ paste the exact message?
frank
Oh yes, you’re right, Frank, I didn’t notice that this file general.css is not part of the wordpress core. It is called by a specific plugin : utlimate branding, from WPMUDEV.
here is a link to this css:
https://www.wordpress-hebergement.fr/wp-content/plugins/ultimate-branding/ultimate-branding-files/modules/custom-admin-bar-files/css/general.css?ver=1.0
I don’t see any particular notice/warning but it breaks the site on safari if it is not excluded from AO
Regards
and how badly does it break? do you get a white page, or the content without any style, or the content with some style? can you post a screenshot with and without general.css excluded?
had a look at the CSS-file itself, and one thing that seems odd (and which might somehow break things somehow) is located at the end;
#wpadminbar li[id^="wp-admin-bar-ub_admin_bar_"] .dashicons{
margin: 0;
}
#wpadminbar li[id^="wp-admin-bar-ub_admin_bar_"]
}
/* 163562-1441435262-au */
you can see that (part) the selector is repeated and that it does not have style attached to it;
#wpadminbar li[id^="wp-admin-bar-ub_admin_bar_"]
In firefox this indeed got me an error; “13:05:19.065 Dangling combinator. Ruleset ignored due to bad selector.1 wordpress:2:1035”
So maybe try to remove that line in the original CSS and see if that somehow magically solves the problem on Safari? If so, this is something the wpmudev-guys would have to look into.
You are completely right.
I removed the duplicate selector and the css file can now be autoptimized.
I opened a ticket here on WPMUDEV and they will fix it asap.
Thanks again, Frank !
Regards
great, thanks for the confirmation. it can be fun to hunt down an issue like this, if closed succesfully 🙂
