Which polyfill caused an ie11 issue? I've been building a stencil compiled component set that has to support ie11, and so far haven't had a problem with their polyfills (but occasionally have had to rewrite sections of my code to get around or)
Lead Developer, business owner, US Army veteran. I build things for the web. My website is a bunch of HTML pages that didn't need a framework. Yours can be too!
url-polyfill, 1.0.14
https://github.com/lifaon74/url-polyfill
MIT Licensed
*/
(function(e){var t=function(){try{return!!Symbol.iterator}catch(e){return false}};...
Now, this is probably from the Stencil 'app' environment, since the components individually work correctly when served on their own (After I fixed the CSS.supports() issue that came from the ion-col component).
Unfortunately I lost the good fight :( Our director wants to make Web-Components our goal over time and we're building with that end-state in mind, but I got a good enough argument (even if it's because of things I disagree with, but we don't have control over it) that now I'm looking at building Vue-Components until we can get rid of IE11. I am OK with this as development is a team sport :D
This is NOT a Stencil issue: This is one of those 'I can probably make it work if I invest enough time and energy', but the time-investment, risk of breakage with multiple errors on ng start --es5 whenever IE is open (again: Stencil app environment) and polyfill breakage is all a bit too much if we HAVE to support IE11 as a PRIMARY (IE: Daily use for all general browsing) browser. (Which is to be expected: Ionic v4 dropped IE11 support, and Stencil is what they used to build all of their components).
I'm still going to continue my journey with Stencil and Vanilla web-components, just not in my current project.... which makes me sad :(
Takeaway for anyone who wants to know if they should use Stencil in their projects: YES. Most of these issues are not with components generated by Stencil, but probably environmental. Our particular use-case just favors speed and stability over rampant innovation (which isn't always a bad thing).
Know the risks (especially if you're pulling in another teams web components) and keep moving forward. Everyone reading this is probably a better engineer than me anyway (or at least that's what the imposter syndrome keeps telling me ;)
Lead Developer, business owner, US Army veteran. I build things for the web. My website is a bunch of HTML pages that didn't need a framework. Yours can be too!
Following-up: My arguments made it, and we knocked down some roadblocks: Stencil/Web Components are a GO! Very excited. I may have some more posts in the future about the journey to try and get some more info out there and help people avoid the mistakes I am sure I'm about to make.
Lead Developer, business owner, US Army veteran. I build things for the web. My website is a bunch of HTML pages that didn't need a framework. Yours can be too!
EDIT: 18 Feb 2016
Something changed between writing this and getting started on the frontend of our app, in the best possible way. I don't know what, but I have not seen a polyfill breakage since my POC. I've got our app up and running on Stencil and have seen very few of these issues. So I guess the ultimate answer is yes!-
I have actually been side-tracked into working on the Java backend since I built the POC, so I have not been able to work on this at all.
I WAS successful in making the argument that full support for IE11 was a very bad idea, and we are going with an alternate, extremely minimal UI specifically for IE (we're talking no-frills bare-bones UI), but the longer we put it off, the closer we get to January 2020, when extended support for Windows 7 ends and I will argue that IE support should go with it.
I actually argued that we shouldn't be supporting it now, either, but you know businesses... There's always one person on the chain that's worried the old guy above him is going to still be using IE, and sees that as a technological issue, not a training one haha!
One suggestion would be to write each component individually and not use their app starter environment, but honestly IE11 is going to give you headaches if you use any browser/tech developed before 2015 and isn't being consistently updated. The browser engine just doesn't have any of the things that have been added to the spec since then...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Which polyfill caused an ie11 issue? I've been building a stencil compiled component set that has to support ie11, and so far haven't had a problem with their polyfills (but occasionally have had to rewrite sections of my code to get around or)
Now, this is probably from the Stencil 'app' environment, since the components individually work correctly when served on their own (After I fixed the CSS.supports() issue that came from the ion-col component).
Unfortunately I lost the good fight :( Our director wants to make Web-Components our goal over time and we're building with that end-state in mind, but I got a good enough argument (even if it's because of things I disagree with, but we don't have control over it) that now I'm looking at building Vue-Components until we can get rid of IE11. I am OK with this as development is a team sport :D
This is NOT a Stencil issue: This is one of those 'I can probably make it work if I invest enough time and energy', but the time-investment, risk of breakage with multiple errors on
ng start --es5whenever IE is open (again: Stencil app environment) and polyfill breakage is all a bit too much if we HAVE to support IE11 as a PRIMARY (IE: Daily use for all general browsing) browser. (Which is to be expected: Ionic v4 dropped IE11 support, and Stencil is what they used to build all of their components).I'm still going to continue my journey with Stencil and Vanilla web-components, just not in my current project.... which makes me sad :(
Takeaway for anyone who wants to know if they should use Stencil in their projects: YES. Most of these issues are not with components generated by Stencil, but probably environmental. Our particular use-case just favors speed and stability over rampant innovation (which isn't always a bad thing).
Know the risks (especially if you're pulling in another teams web components) and keep moving forward. Everyone reading this is probably a better engineer than me anyway (or at least that's what the imposter syndrome keeps telling me ;)
Following-up: My arguments made it, and we knocked down some roadblocks: Stencil/Web Components are a GO! Very excited. I may have some more posts in the future about the journey to try and get some more info out there and help people avoid the mistakes I am sure I'm about to make.
Fingers crossed people, let's make it happen!
Have you eventually solved those issues and made stencils app working in ie11? Seems like I encountered the same problems
EDIT: 18 Feb 2016
Something changed between writing this and getting started on the frontend of our app, in the best possible way. I don't know what, but I have not seen a polyfill breakage since my POC. I've got our app up and running on Stencil and have seen very few of these issues. So I guess the ultimate answer is yes!-
I have actually been side-tracked into working on the Java backend since I built the POC, so I have not been able to work on this at all.
I WAS successful in making the argument that full support for IE11 was a very bad idea, and we are going with an alternate, extremely minimal UI specifically for IE (we're talking no-frills bare-bones UI), but the longer we put it off, the closer we get to January 2020, when extended support for Windows 7 ends and I will argue that IE support should go with it.
I actually argued that we shouldn't be supporting it now, either, but you know businesses... There's always one person on the chain that's worried the old guy above him is going to still be using IE, and sees that as a technological issue, not a training one haha!
One suggestion would be to write each component individually and not use their app starter environment, but honestly IE11 is going to give you headaches if you use any browser/tech developed before 2015 and isn't being consistently updated. The browser engine just doesn't have any of the things that have been added to the spec since then...