Absolutely, but if someone is looking for a Polymer dev, why not :).
Btw, Firefox is releasing shadow DOM and custom elements in October, so only Edge is left out soon (which you can polyfill technically, although with bad performance hits)
That's what polyfills are for, and they're slowly being replaced as specs are adopted by browser vendors. FF just activated ShadowDOM support in their nightly build. Webcomponents moved to NPM module imports, which cleared a big hurdle, and a modified HTML imports spec is still under discussion. So, the color chart doesn't really tell the whole story.
In answer to the fee increase, I already have, and, if anything, I'm turning away work on Polymer PWAs and headless projects.
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.
While I lean towards yes, I also wanted to point out that Custom Elements still has very sparing browser support caniuse.com/#feat=custom-elementsv1
Absolutely, but if someone is looking for a Polymer dev, why not :).
Btw, Firefox is releasing shadow DOM and custom elements in October, so only Edge is left out soon (which you can polyfill technically, although with bad performance hits)
BTW the light green bar does not mean it's buggy btw, it's just an improved version of custom elements.
the light green represents missing features from the spec and FF has them behind a flag
That's what polyfills are for, and they're slowly being replaced as specs are adopted by browser vendors. FF just activated ShadowDOM support in their nightly build. Webcomponents moved to NPM module imports, which cleared a big hurdle, and a modified HTML imports spec is still under discussion. So, the color chart doesn't really tell the whole story.
In answer to the fee increase, I already have, and, if anything, I'm turning away work on Polymer PWAs and headless projects.