|
I'm seeing sporadic success/failure this morning (with Firefox on Windows), so I assume it's a W3C issue. I'll wait a while to see if the situation improves before investigating too deeply.
I've never been a fan of hardcoding this sort of external internet dependence into a program anyway. It's way too fragile when the website in question is not under your control.
I had a temporary CSS3 validation plugin that did much the same thing (before Sigil included the CSS2/2.1/3 preference setting). Perhaps I should dust it off and make it full featured, so that we can remove the fragile functionality from Sigil itself. That way if something goes wonky, you release a new plugin instead of invalidating features of previous versions of Sigil (moving forward).
|