Thanks for reporting this. I can confirm I’m experiencing the same thing. I’ve gone ahead and created a high priority ticket for this so it should get taken care of soon.
Thanks for confirming, esteban – good catch here. This is, as Jonah noted, a high priority for us. Now that we’re back on a regular release cycle and are obviously moving quicker for the short-term than just monthly releases, we should have a 3.0.2 build out real soon here. Stay tuned and thanks again for your support/patience.
I just wanted to follow-up to confirm that we DO have a fix in the works for this, and it’s done/awaiting deployment in 3.0.2. Whether that’ll go out this afternoon or first thing Monday morning depends on how quickly we can get through the final QA/packaging, but know it’s coming. Thanks to everyone for their patience so far.