@darksky @hnyman I can confirm this behavior with a build from roughly 2 hours ago (from time of this post)
I have a firewall rule within traffice rules which blocks an range specific to IoTs to be blocked from Internet. After updating to a post FW4 build, devices in that range are able to access the Internet. Flipping back to build just prior to the FW4 becoming default (i.e. FW3 build), and Internet is again blocked for those IPs.
Setup:
Protocol: TCP/UDP
Source Zone: lan
Source Addresses: 192.168.1.208/28 and 192.168.1.224/28
Destination Zone: wan
Action: reject
All other fields are default.