There was an ordering problem between wb-values and wb-row when we stash them in the block header. Apparently processing siblings in order is not actually required by the Custom Element spec. Anyway, this uses less of the Custom Element API and seems to work across browsers now.
There was an ordering problem between
wb-values
andwb-row
when we stash them in the block header. Apparently processing siblings in order is not actually required by the Custom Element spec. Anyway, this uses less of the Custom Element API and seems to work across browsers now.