@sindy did respond, but his response was copied to RouterOS bridge mysteries discussed - incl. diagrams - #17 by sindy
When the bridge is "created" it creates an interaface within the router block that the router uses to communicate with the switch like entity via the router facing port of the switch like entity.
See this thread Slow Hex file transfer speed and my interpretation of how the pieces fit together in this post Slow Hex file transfer speed - #19 by Buckeye which specifically discusses what frame-type and ingress-filtering on the bridge statement apply to (the router facing port of the virtual switch).
Also vlan-filtering on the bridge turns on vlan aware mode on the virtual switch, where it makes the switch segregate traffic into vlan broadcast domains, and makes it classify all inbound traffic into a specific single broadcast domain based on either vlan-tag or pvid, or to drop the traffic.
The "bridge table" is part of the virtual switch when vlan aware mode is active, i.e. vlan-filtering=yes as is the bridge host table (mac address table that is built by learning, or adding static mac entries) that ties mac addresses to a bridge/switch port