• Use the current parser location for CSS error

    … rather than the start location of the current construct.
    This likely places the error just *after* of the unexpected token
    whereas before would be best, but that’s likely a much bigger change.
    
    See https://bugzilla.mozilla.org/show_bug.cgi?id=1378861
    SimonSapin committed Oct 10, 2017