Viewing profile — ebidel

Yes and no. In some cases (3rd party content that you don't control), there's no way to know what script/iframe is going to do/use. For example, ads script that uses `document.writ…

full example of screenshoting a DOM element: https://github.com/GoogleChrome/puppeteer/issues/306#issueco...

Make sure you're using Chrome 59. If you don't have that yet, try Chrome Canary.

It's just a bug :) https://news.ycombinator.com/item?id=14240460

As noted, you'll need the --disable-gpu flag for now. Hopefully that will go away around ~Chrome 60. See - https://bugs.chromium.org/p/chromium/issues/detail?id=546953... - https:/…

FWIW, we created the Github issue tracker b/c it's a bit more approachable for everyone. Github is also a much better place for discussions.

Windows support is coming. You can follow along at https://bugs.chromium.org/p/chromium/issues/detail?id=686608

If your app uses a huge amount of code, then yes. But that's really the fault of the app developer. Not the library. What developers often do is pull in a ton of components from th…

Also relevant: "Cache-Aware Server Push (Client Side)" https://docs.google.com/document/d/1HhmyzKUPuWcCs8wG_GLSu3mv... The Chrome team is hashing out potential solutions to the ser…

In using shadow DOM, one thing that's become clear is that it is a developer productivity tool (built in the browser). With React, you have to use inline styles ( https://facebook.…

Non-comprehensive list of Google properties and Chrome-team efforts using: https://github.com/Polymer/polymer/wiki/Who's-using-Polymer%... Obviously doesn't include stuff in the wo…

Polymer itself is 47KB. If you add the web component polyfills (16KB), that's 63KB minified and gzipped. I tend not to consider the polyfills because they're not Polymer and are a …

Perspective is important :) Putting 1000 material design inputs on a page isn't something a sane web app would do. The same is true for a native app. Re. "bloat" of components. I t…

MS: https://dev.modern.ie/platform/status/shadowdom/ "we intend to begin development soon" FF: https://bugzilla.mozilla.org/show_bug.cgi?id=1205323

Yep, service worker is amazingly powerful! FWIW, Chrome has a bug where SW doesn't intercept URLs changed using history.pushState(). If you're using the web app in Chrome 40, turni…

It's still behind the web components flag in FF nightly. The master bug for web components is: https://bugzilla.mozilla.org/show_bug.cgi?id=811542

Beers! It's 100% bizarre to think about elements that don't render UI. Honestly, I'm still wrapping my head around it. If you think about it though, there are plenty examples today…

These are legitimate concerns to have. There are many new technologies at play in this space and a lot of new concepts. > What really remains to be seen is whether this reduces or …

Can you explain why it feels heavy? I would love to know more. Polymer's entire stack is a la carte: * platform.js - polyfills if you just want to use vanilla web component apis, t…

It's a common misconception that Shadow DOM is required to create a "web component". What it brings to the table is style and dom encapsulation. Not using it means components won't…

Adding powerful new APIs to the web platform benefits more than just Angular, no? The set of evolving standards-based technologies behind "web components" (templates, Shadow DOM, H…

The Custom Elements[1] and Shadow DOM[2] specifications have little to do with each other. The former is useful for defining new elements in HTML, along with properties and methods…

See my post [1] on SO on "Polymer elements (e.g. web components) vs. Angular directives". Essentially, Angular directives allow you to create new elements in HTML. That's done thro…