Parent node uses CSS transform:translate (0, 0) when position:fixed is not valid in Chrome browser

Today in the mobile page, inadvertently found a Chrome browser under a bug, in the use of CSS3 's transform:translate (0, 0) attribute to the location of Node A conversion, there is a node below a word node B, node B uses the position : fixed positioning, according to the common sense node B should be hanging in the browser window view, will not follow the scroll bar and scroll, but this effect in the Chrome browser is not valid, tested in IE11, Firefox, Safari, no problem, The effect in opera is exactly the same as in Chrome.

To summarize: Under Chrome and opera browsers, use CSS3 's transform:translate (0, 0) to convert location nodes, all of which have no effect on the location function of any descendant nodes using position:fixed targeting.