We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
"After removing the "fractional_edit" class from the span tag containing said fields, the field appears but then disappears again when hovered over."
The reason why it disappears again after hovering over it is because a "fractional_edit_nonover" class is appended to the span tag via Javascript. This class, as well as "fractional_edit" share the same value of "display:inline-block".
The only way I was able to show the fractional editable field and keep it showing (even after hovering) was to completely remove the "display:inline-block" value from global.css
You apply an rgba color to your h1 and h2 selectors, with the final component of 0. i.e. fully translucent. i.e. invisible.
I think Chrome is only applying translucent font colors to a block context, so inline-block is creating that block context. It may be in the specs, I'm not sure, but it's a very esoteric issue.
(Click to enlarge)
(Click to enlarge)
(Click to enlarge)
#3708 - Fractional editable fields disappear in Chrome
"After removing the "fractional_edit" class from the span tag containing said fields, the field appears but then disappears again when hovered over."
The reason why it disappears again after hovering over it is because a "fractional_edit_nonover" class is appended to the span tag via Javascript. This class, as well as "fractional_edit" share the same value of "display:inline-block".
The only way I was able to show the fractional editable field and keep it showing (even after hovering) was to completely remove the "display:inline-block" value from global.css
You apply an rgba color to your h1 and h2 selectors, with the final component of 0. i.e. fully translucent. i.e. invisible.
I think Chrome is only applying translucent font colors to a block context, so inline-block is creating that block context. It may be in the specs, I'm not sure, but it's a very esoteric issue.