I played with the node a bit, it seems to work as expected.

This is how the node looks like now.

@Omar Emara (OmarSquircleArt) After looking at this new mapping node, I'm thinking that the rotation node patch D3789 should just be implemented in this node but as an alternative type called rotate.

void mapping_rotate(vec3 vector, vec3 location, vec3 rotation, vec3 scale, out vec3 result)
{
  result = (euler_to_mat3(rotation) * (vector - location) + location) * scale;
}

Of course, in the future it would be nice to have matrix support in the shader nodes.

A file to test backward compatibility:

As @Charlie Jolly (charlie) noted, the mapping node rotation doesn't match the texture mapping rotation for some reason. Our Euler to matrix conversion follow the same order XYZ, and the functions are implemented based on the matrix from the wikipedia page on the topic, that is:

@Omar Emara (OmarSquircleArt) I can only guess it may have something to do with Blender being right handed.

https://stackoverflow.com/questions/31191752/right-handed-euler-angles-xyz-to-left-handed-euler-angles-xyz

In D5541#126897, @Omar Emara (OmarSquircleArt) wrote:

As @Charlie Jolly (charlie) noted, the mapping node rotation doesn't match the texture mapping rotation for some reason. Our Euler to matrix conversion follow the same order XYZ, and the functions are implemented based on the matrix from the wikipedia page on the topic, that is:

That is a ZYX rotation. Note the order of operations: X * (Y * (Z * vector))

A file to test backward compatibility when the mapping node properties are animated.

This patch rewrites the Mapping node to support dynamic inputs. The
Max and Min options have been removed. They can be added as Min and
Max Vector Math nodes manually.

The problem is that Min and Max Vector Math Nodes don't really do the job as they should, instead all values are returned as Black.

Blender 2.80:

Blender 2.81.8:

EDIT:
OK so I dug poked a little tiny bit and wondered what if I flip to first maximum, then minimum, and voila, it works. But how is it possible that works? In any case, the way Blender 2.81.8 updates .blends right now is wrong. It puts Minimum first at 0 0 0, then Maximum at 1 1 1. Some math genius please inquire.

Please report bugs in the tracker:
https://developer.blender.org/maniphest/task/edit/form/1/