I ran into this situation and got quite the headache trying to fix it. I'm not sure what the best solution would be, but thought I'd bring it to your attention so you can consider.
The problem arises when:
- An orbicular element is under the effect of
ng-hide or ng-show (or anything else which sets CSS of display:none).
- The orbicular element is created after the element has been hidden, not on load. For example, this can happen to a collection that is populated in the same digest cycle as the truth condition to show the collection.
This example shows the behavior. In this situation, the offsetWidth value is 0 because the element is not displayed, so Orbicular calculates the wrong font size and ends up hiding the element (even after display is changed and the element should be visible).
I ran into this situation and got quite the headache trying to fix it. I'm not sure what the best solution would be, but thought I'd bring it to your attention so you can consider.
The problem arises when:
ng-hideorng-show(or anything else which sets CSS ofdisplay:none).This example shows the behavior. In this situation, the
offsetWidthvalue is 0 because the element is not displayed, so Orbicular calculates the wrong font size and ends up hiding the element (even afterdisplayis changed and the element should be visible).