Routes to subnets in other routing tables. Why doesn't this work?

RouterOS Beginner Basics
1

ROS 7.15.3
ISP1 ether1, ISP2 ether2, LAN1 ether3 (192.168.88.0/24), LAN2 ether4 (192.168.99.0/24)

routing table tab-1
routing table tab-2

Routes to subnets in tab-1, tab-2 routing tables

add dst-address=192.168.88.0/24 gateway=ether3 routing-table=tab-1
add dst-address=192.168.99.0/24 gateway=ether4 routing-table=tab-1

add dst-address=192.168.88.0/24 gateway=ether3 routing-table=tab-2
add dst-address=192.168.99.0/24 gateway=ether4 routing-table=tab-2

Why doesn’t this work?

2

Is this some sort of joke??
Why are you adding special table for routes that already exist on the router.
When you create a subnet a route is automagically created

add dst-address=192.168.88.0/24 gateway=192.168.88.1 routing-table=main
add dst-address=192.168.99.0/24 gateway=192.168.88.1 routing-table=main

So the question becomes, what traffic requirement, user or device, require additional routes?

3

For example, incoming connection from isp2 use routing table tab-2

4

Those routes are completely unnecessary if you do not use VRFs.
But if you use VRFs then here is an example how to properly do it
https://help.mikrotik.com/docs/pages/viewpage.action?pageId=328206#VirtualRoutingandForwarding(VRF)-StaticVRF-LiteConnectedrouteleaking

5

The question was different!
I want to do without an exception to the rules of the table Mangle, do not use, for example

# ip firewall mangle
#0 add action=accept chain=prerouting  dst-address=192.168.188.0/24 src-address=192.168.99.0/24
#1 add action=accept chain=prerouting  dst-address=192.168.99.0/24 src-address=192.168.188.0/24

That is, do not exclude from marking!

6

I will say it for the last time, stop with the config speak.
Talk plainly to describe requirements based on user or device traffic.
If you cannot clearly describe traffic requirements there is no point in even starting modifying or creating a config.