Open jejay opened 8 years ago
It should be said that the v-tabs directive is not working anymore correctly with the div fallback. This is mainly a css issue. For reproducing the working "fallback" you should leave <v-tabs>
as it is and only change <v-page(s)>
to <div vpage(s)>
and also the css accordingly.
I used the chrome 51.
Sry for the inconvenieunce, but I found out the issue is a css related issue.. The problem does not lie in the elements custom name but rahter in some css that the v-tabs-directive contains.
All what is needed to reproduce the error is:
<div style="display:none">
<circular-slider
class='my-slider'
animate='true'
on-slide='onSlide'
on-slide-end='onSlideEnd'
min="0"
max="360"
value="subject.selected.rotation">
</circular-slider>
</div>
When the slider is used within a directive with custom element, for example the https://github.com/LukaszWatroba/v-tabs, the following error is thrown:
TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'
The corresponding code is:
A temporary solution is to use divs as fallback:
This does work as expected.