Jake Champion

@romainmenke could you send a link to how core-web is doing the useragent parsing? I would like to see if we can incorporate that into Financial-Times/polyfill-useragent-normaliser or Financial-Times/useragent_parser

PR for this work --> https://github.com/Financial-Times/polyfill-library/pull/627

@CemDemirkartal What you suggest is not a polyfill as that is not how `:scope` is intended to work according to the specification. Your suggestion would cause bugs in web applications...

@jonathantneal sorry for the very late response. I see that the element-qsa-scope polyfill has stated IE support is 8 - 11, have you tested it on IE 7 at all?...

@jonathantneal Excellent! If you could provide a version without the in-built feature detection that would be really helpful and mean we can pull in your polyfill directly from npm. :-)

@jonathantneal It doesn't need to be listed as the main file, we can pull any file from the npm package :-) It is preferable to have it authored in ES5/ES3...

Hi @chenyulun can you try with npm instead of yarn? I tried and it is all working: ``` ❯ git checkout v3.108.0 Note: switching to 'v3.108.0'. HEAD is now at...

https://github.com/Financial-Times/polyfill-library/blob/f0a9bb1646f076eebe0174f39e890f6e877ce6bd/polyfills/Symbol/asyncIterator/config.toml#L15 That's odd to see because we configured that polyfill to not be served to iOS 13, it is only served to iOS 11 and lower. How are you making...

@CheloXL Would that be the same as the `all` alias we have? https://polyfill.io/v3/polyfill.min.js?features=all

This states that IE 4 and above have Element.prototype.innerHTML -- https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML#Browser_compatibility