Support ie #87
Support ie #87
Conversation
| @@ -1 +1,43 @@ | |||
| .dragging{z-index:111!important}.block{position:absolute;z-index:9}.indicator{width:12px;height:12px;border-radius:60px;background-color:#217ce8;margin-top:-5px;opacity:1;transition:all .3s cubic-bezier(.05,.03,.35,1);transform:scale(1);position:absolute;z-index:2}.invisible{opacity:0!important;transform:scale(0)}.indicator:after{content:"";display:block;width:12px;height:12px;background-color:#217ce8;transform:scale(1.7);opacity:.2;border-radius:60px}.arrowblock{position:absolute;width:100%;overflow:visible;pointer-events:none}.arrowblock svg{width: -webkit-fill-available;overflow: visible;} No newline at end of file | |||
| .dragging { | |||
|
IMO - instead of supporting IE should rework the code base to be a web component. Use shadowDOM and be a really nice re-usable HTML element with ondrag attributes etc... See: https://gs.statcounter.com/. - globally in Jan 2021 IE saw less than 1% of traffic.... With Edge being Chromium based it's never been a better time in the history of the web to use the excellent tools available since the fall of IE6's rain of terror. Firefox, Chromium and Safari all support class, const, let, () => { console.log("and even this") }... that said I'm just having fun and all good work should be recognized just saying it might be cool to push to a world of no more IE and moving beyond ES5 to ES6. - just my fly by 2 cents |
4 participants
No description provided.