I just used a Webflow layout in a Meteor app, which handles packaging up all the bits to be sent to the client and shipping them down. Instead of manually defining
<link rel="stylesheet" ...>, Meteor minifies everything, sends it to the browser, and evaluates it for you.
One quirk that comes as a result is that you no longer control load order of resources by where in the document they appear. You can control the load order by naming / structuring your app such that Meteor will minify things in whatever order you want, but you are encouraged to make sure resources can be loaded in any order instead.
So, to the point: I've discovered that the load order of webflow.css and .webflow.css is actually significant. That was a bit of a surprise, since I learned the hard way years ago about CSS' "specificity" rules. I guess both files contain equally-specific rules.
Would love to know if I'm wrong about this - but otherwise it'd be a nice (albeit low priority) thing to fix.