robdodson

Joined 15 years ago

Karma

127

Submissions

Member since

Nov 12

View on Hacker News

Recent submissions

I Built My Mobile Second Brain robdodson.me

1 robdodson 8 months ago 0 comments

My Second Brain Never Worked. Then I Gave It a Gardener robdodson.me

5 robdodson 9 months ago 1 comments

Clawdbot's Missing Layers robdodson.me

2 robdodson 9 months ago 0 comments

Comment · 6 years ago

Post author here

Totally hear you on the need to make the elements styleable. That's the next phase of work that's being undertaken, specifically starting with <select>. Take a look at the talk that's linked from the article for a more in-depth explanation of the future phases.

Comment · 8 years ago

I think my comment may get buried but I'll try anyway :)

I'm one of the engineers working on web.dev and recently we had some issues with the way the report was being generated (detail here: https://medium.com/dev-channel/web-dev-status-update-14th-no...)

Specifically, there were audits flagged as "not applicable" and the alpha version of Lighthouse was instead flagging them as failures. That's why it looked like it was telling you to add audio or images—it was actually saying those audits are not applicable because your site doesn't use audio or images. I think that bug has been fixed in Lighthouse but feel free to reply to this comment if you're still seeing it.

We've also temporarily turned off the PWA audits—they were having some bugs of their own based on the infrastructure they were running on. Based on the feedback in this thread we'll look into making them configurable so folks can choose if they want to run them.

We'll also be opening up the repo shortly so folks can file bugs there directly.

Comment · 8 years ago

Hey folks, I wanted to share a quick status update to let y'all know which issues we're seeing and working on. Apologies for the hiccups and thank you all for trying the beta!

https://medium.com/dev-channel/web-dev-status-update-11-12-1...

Comment · 8 years ago

Ah yeah that's something we want to fix. If you're signed in it keeps the report around but if you're signed-out it's stateless. It's definitely on our to-do list to fix.

Comment · 8 years ago

Yep that's our bad. We accidentally started prefixing all of the urls with https we've fixed the bug but haven't shipped it yet cuz we're in code freeze

Comment · 8 years ago

Heyo! One of the web.dev devs here. The new web.dev site is an experiment from our team to see if we can improve the interactivity of our docs. We link to developers.google.com/web in a number of places. Over time, if folks seem to enjoy the web.dev model, we may explore moving more of our docs over there. But for now it's just a fun experiment

Comment · 8 years ago

Yep that's our mistake (one of the web.dev devs). We auto added https to every URL. Oops! Gonna fix that as soon as we are out of our code freeze

Comment · 9 years ago

For anyone interested, I wrote up a response: https://robdodson.me/regarding-the-broken-promise-of-web-com...

Kinda used it as an attempt to address some bigger questions around Web Components I've seen come up a bunch. Curious what you all think.

Comment · 10 years ago

I think you can bring the time to initial interactive experience way down by using Polymer CLI. Looking at wedding-app.html it looks like it's loading a lot of elements which aren't on screen yet.

Take a look at the app-drawer-template example and note the line that lazy loads element definitions when pages change: https://github.com/Polymer/app-drawer-template/blob/master/s...

If you use the CLI you can create a polymer.json file that lets you fragment up your site: https://github.com/Polymer/app-drawer-template/blob/master/p... This way you'll create separate vulcanized bundles and you can lazy load them right when the user clicks on the section, hopefully improving that first load experience.