There is no reason for h264 decode to take much power at all, it's all done in hardware now (or should be done in hardware).

In other words, Safari's power number isn't surprising but I don't know how chrome manages to use so much processing power. Even my cell phone can decode 1080p60 without catching fire but chrome manages to bring a $2200 laptop to it's knees doing it.