Unknown pseudo-class 'link' about premailer.net HOT 3 CLOSED

I think this error is coming up from CsQuery here - and it makes sense, you've asked the selector to handle something it can't handle (irrespective of it's validity).

However, I don't think we should fall on our ass because of that, I was thinking of the following:

• We search the CSS for any unsupported selectors.
• We strip them out.
• We leave a HTML comment in the document to let the user know this has happened? (I personally hate the silent actions that just leave you clueless as to what's happened)
• Carry on processing everything else as normal.

I'll put together a pull request shortly.

from premailer.net.

I agree, never fail except for situations where an ArgumentException is suitable.

The comments in the HTML is fine for now, but I'd like to move to a concept of a more detailed result object that could look like this:

{
    Output: "premailed output",
    Warnings: [],
    Errors: []
}

The same goes for the parameters when calling the premailer method, as more information such as base URL is needed to fix #8 and #5.

Along with the option to remove style blocks, ignore selectors, base URL etc. it might be more clean to have a class for this.

from premailer.net.

Hey @martinnormark - sounds good on the return type for MoveCssInline. I've created #27 so it's on our radar. This will be no problem to add.

from premailer.net.