Even though the attribute's effect gets activated for any value of the attribute, this way it's easier for anyone looking at the DOM to figure out what the visibility of the node is.
This was originally overwritten when merging in v3.14.1.
New Chrome and Android use the full value declaration for font properties such as `textDecoration`. They return: `underline solid rgb(0, 0, 0)` Instead of just: `underline`
This test is a known failure on Android 4.4.x, due to how Chrome for Android now adds additional padding pixels to the ScrollView's `boundingBox`. This doesn't affect the general use case, though this test and the one above it should likely be refactored.
This problem occurs when you try to set an opacity to 1 using node.setStyle() method on IE. It has adapted to change an opacity only if less than 1, but we should change an opacity, even if it passed 1. Fix #1469.