Message actions from other widgets should also act on the floor widget if it is connected to the same data framework.
For example I currently have an Experience with three widgets: a (floor-enabled) map, a list and a floor filter. When I select a building from the list, I'm able to pan to the corresponding on the map via the message action. The problem is that the floor filter widget does not react and stays on whichever building it was last on.
This removes the ease of being able to jump around buildings first, then internally within floors. The list is made redundant as the user still has to select the correct building on the floor filter 'browse', but this browse menu is less customisable and not as intuative to navigate, so doesn't make a good replacement for the list widget.
